I find asyncore to be quite useful, however, it is currently geared to having a single main loop. It uses a global socket map that all asyncore dispatchers register with. I have an application in which I want to have multiple socket maps. I propose that we start moving toward a model in which selection of a socket map and control of the asyncore loop is a bit more explicit. If no one objects, I'll work up some initial patches. Who should I submit these to? Sam? Should the medusa public CVS form the basis? Jim -- Jim Fulton mailto:jim@digicool.com Python Powered! Technical Director (888) 344-4332 http://www.python.org Digital Creations http://www.digicool.com http://www.zope.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.
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