* Richard Tew <[EMAIL PROTECTED]> [2007-02-12 13:46:43 +0000]: > I currently use Windows. By using asyncore and monkeypatching in a > replacement socket module based on it [1] I can give users of Stackless > socket operations which invisibly block at the microthread level allowing > the scheduler to continue to run. However there is no support for > asynchronous file IO. Now I can monkeypatch in a replacement file > object which uses IO completion ports [2], but at that stage I need to > poll two different resources for events. In order to avoid this it makes > sense to stop using asyncore for sockets and to write a new > replacement socket object based on IO completion ports.
...sounds kinda like the Twisted reactor. Except the IOCP implementation thereof is still underway, I believe. > Perhaps there is a better way. And I of course have no concept of > how this might be done on other platforms. Building on an existing framework that does this seems better than reinventing the wheel, for something of this magnitude. -- mithrandi, i Ainil en-Balandor, a faer Ambar
signature.asc
Description: Digital signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
