On Sunday, 9 March 2014 04:31:38 UTC-7, hynek wrote:
>
> On 9 Mar 2014, at 12:20, Chris Withers wrote:
>
> > 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 asyn
We've been building a fairly large system for the past 2 years. Hopefully
going into public beta soon. It deals with a lot of the same concepts as
you're talking about. We've got a website, a twisted daemon and a celery
daemon.
The big tip I can give you is to consider how much you'd like th
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 buil
On 09/03/2014 11:31, Hynek Schlawack wrote:
On 9 Mar 2014, at 12:20, Chris Withers wrote:
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
possibi
On 9 Mar 2014, at 12:20, Chris Withers wrote:
> 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
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
us
