Marcus Low wrote: > Hi Waldemar, > > Thanks, i have bought the twisted book and the journey begin. The COM was > optimal for windows because its asynch api winsock2 and > that beats berkeley socket "select" anyday on Windows,
That is superstitious nonsense. The asynchronous winsock API had to be invented because Windows 3.x did not support pre-emptive multitasking. It has no inherent performance advantage. Now that Windows has threads, many people argue that the synchronous API is the better choice. In the end, it comes down to personal preference. -- Tim Roberts, [EMAIL PROTECTED] Providenza & Boekelheide, Inc. _______________________________________________ python-win32 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-win32
