Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #68754 > unrolled thread

which async framework? - a summary

Started byChris Withers <chris@simplistix.co.uk>
First post2014-03-21 18:34 +0000
Last post2014-03-21 18:34 +0000
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  which async framework? - a summary Chris Withers <chris@simplistix.co.uk> - 2014-03-21 18:34 +0000

#68754 — which async framework? - a summary

FromChris Withers <chris@simplistix.co.uk>
Date2014-03-21 18:34 +0000
Subjectwhich async framework? - a summary
Message-ID<mailman.8387.1395477640.18130.python-list@python.org>
On 14/03/2014 00:36, Tim Chase wrote:
> On 2014-03-14 00:25, Chris Withers wrote:
>> I've been pleasantly surprised by the succinct, well reasoned and
>> respectful replies from each of the communities!
>
> As one who doesn't lurk on the other lists, is there a nice executive
> summary of their responses?

Well, of course, each person recommended their own framework.

The short version was:

- tornado is a web server, if you're not using it, the async stuff is 
better developed elsewhere

- asyncio is very new, not a lot of protocols out in the wild and not 
much battle testing

- twisted is been around the block a lot, huge amounts of support and an 
active, knowledgeable community. Can feel crufty and old in parts, mind

The community bit swung it for me, so I've opted for Twisted, if I ever 
get a chance to work on the project in question ;-)

Chris

-- 
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web