Tim, http://www.patentstorm.us/patents/6223207-description.html
The advantage of scalability and performance of using IOCP/asynch for writing servers vs berkeley style select in Windows is a known thing for windows programmers. ICOP is built right into the Windows system drivers with the purpose of giving this advantage. It has nothing to do with what 3.x have or not, this mechanism is introduce for Windows NT line of operating systems (leading to 2k, xp, vista) It doesn't comes down to "personal preference", that choice unfortunately is the choice of ignorant programmers. > It has no inherent performance advantage : Tim Roberts I would suggest you close this thread, if you chose to reply this thread with information from Planet-Megatron, I would not have the courtesy to reply. Marcus. ----- Original Message ----- From: "Tim Roberts" <[EMAIL PROTECTED]> To: "Python-Win32 List" <python-win32@python.org> Sent: Friday, April 04, 2008 12:44 AM Subject: Re: [python-win32] A shameless COM question > 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 > python-win32@python.org > http://mail.python.org/mailman/listinfo/python-win32 _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
