>> it is safe to define NO_ADV_MT when a TWSocket instance is use from a
>> single thread only
>
> It seems I missed that one. I have checked the code and it seems to me
> it is only there for if you want to call TWSocket methods from another
> thread context as where it is created in. Is that cor
Hello Francois,
> it is safe to define NO_ADV_MT when a TWSocket instance is use from a
> single thread only
It seems I missed that one. I have checked the code and it seems to me
it is only there for if you want to call TWSocket methods from another
thread context as where it is created in. Is t
- Original Message -
From: "Francois Piette" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Friday, September 02, 2005 12:30 PM
Subject: Re: [twsocket] NO_ADV_MT symbol
>> > IMO it is better design to have all access to a given
>> > comp
> > IMO it is better design to have all access to a given
> > component from only one thread. And in that case, you can
> > define NO_ADV_MT to have better performances because you
> > avoid using a critical section.
>
> Thank you, this answers my questions.
>
> I use 2 servers and some clients in
> IMO it is better design to have all access to a given
> component from only one thread. And in that case, you can
> define NO_ADV_MT to have better performances because you
> avoid using a critical section.
Thank you, this answers my questions.
I use 2 servers and some clients in same exe, b
> I wonder when it is safe to define NO_ADV_MT.
>
> Must I not define NO_ADV_MT at all when I use threads?
>
> What if I use a socketserver in one thread and another socketserver in
> another thread and there is no interaction between the threads? The client
> connections always stays within the t
I wonder when it is safe to define NO_ADV_MT.
Must I not define NO_ADV_MT at all when I use threads?
What if I use a socketserver in one thread and another socketserver in
another thread and there is no interaction between the threads? The client
connections always stays within the threads.
