* Richard Tew <richard.m.tew at gmail.com> [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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://mail.python.org/pipermail/python-dev/attachments/20070212/fd2311c5/attachment.pgp
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4