The new Socket.XXXAsync APIs were added to the .NET FW to "...provide an
alternative asynchronous pattern that can be used by specialized
high-performance socket applications. This class was specifically designed
for network server applications that require high performance." (MSDN)

I was quite disappointed when I saw the mono implementation of this API -
create a new thread for each XXXAsync call. This cannot produce a good

Did you test that this implementation is really more performant than the
BeginXX/EndXX async pattern?
Is there any plan to rewrite this code in the future?
View this message in context: 
Sent from the Mono - General mailing list archive at Nabble.com.

Mono-list maillist  -  Mono-list@lists.ximian.com

Reply via email to