Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #68243
| From | Marko Rauhamaa <marko@pacujo.net> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: which async framework? |
| Date | 2014-03-12 00:18 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <87bnxcnzv3.fsf@elektro.pacujo.net> (permalink) |
| References | <531E22DF.7030709@simplistix.co.uk> <1733040935416225908.878896sturla.molden-gmail.com@news.gmane.org> <loom.20140311T170030-477@post.gmane.org> <mailman.8055.1394559893.18130.python-list@python.org> <bo9f4lFacnnU1@mid.individual.net> |
Gregory Ewing <greg.ewing@canterbury.ac.nz>: > It's not "epoll function calls" that the coroutine style is intended > to replace, it's complex systems of chained callbacks. They're > supposed to make that kind of logic *easier* to follow. If you haven't > had that experience, it may be because you've only dealt with simple > cases. The coroutines are definitely something to get into, although I'm skeptical as well. Epoll and the associated idioms have been with us for a long time and are well understood. As for "easy to follow," unfortunately the complexities of network state machines cannot be abstracted out, and the result is never exactly easy to the eye. Marko
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: which async framework? Sturla Molden <sturla.molden@gmail.com> - 2014-03-11 17:44 +0000
Re: which async framework? Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-03-12 10:56 +1300
Re: which async framework? Marko Rauhamaa <marko@pacujo.net> - 2014-03-12 00:18 +0200
csiph-web