On 03/09/2014 04:20 AM, Chris Withers wrote:
Hi All,
So, one of the projects I'm playing with at the moment is a big ball
of asynchronous networking (tonnes of protocols, some tcp, some
multicast) which I want to stick a webapi onto (normal requests +
websocket).
What's the best way to build the web side of this? I think I'd like to
use pyramid for the normal request/response parts of the web api and
some async framework for the websock part of it along with all the
other network stuff. Does that sound feasible?
Aside from that, what's people's experience/recommendations when it
comes to the plethora of async stuff currently available?
twisted, tornado, tulip or even good old fashioned asyncore seem like
possibilities, I'm wondering which way to go
Any other advice people have in this area?
cheers,
Chris
The last time I had to do this, I just ran pyramid under gevent and used
gevent's async stuff.
AM
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
