which async framework? - a summary

Date	2014-03-21 18:34 +0000
From	Chris Withers <chris@simplistix.co.uk>
Subject	which async framework? - a summary
References	(1 earlier) <lflcha$2mf$1@ger.gmane.org> <531EC0E6.10402@simplistix.co.uk> <lfnotf$i2a$1@ger.gmane.org> <53224C89.5050503@simplistix.co.uk> <20140313193634.3767ddfc@bigbox.christie.dr>
Newsgroups	comp.lang.python
Message-ID	<mailman.8387.1395477640.18130.python-list@python.org> (permalink)

Show all headers | View raw

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

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

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

csiph-web