Hi Gonzalo,

>> Inside the "threadPool" the following code:
>>
>>  threadDone.WaitOne(PoolGrowDelay, false);
>>
>> Makes thread creation wait 500ms (I guess just forcing the CPU to switch
>> to another one) each time a new thread is created (when the pool is
>> growing).
>>
>> If you remove it, connection problems go away, but I guess it's not the
>> right way to implement it.
>>     
>
> That should be modified to make use of the .NET ThreadPool and use
> asynchronous operations for accept, read and write (this last one is not
> "mandatory"). There's code in xsp that illustrates the way it should be
> done.
>
>   
Which ThreadPool exactly should be used?

Could you point me to the right code in xsp?

Thanks,

pablo
_______________________________________________
Mono-devel-list mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Reply via email to