[pylons-discuss] Re: advice for sending events back to javascript from pyramid (redis, polling, asyc, etc)

we have a similar situation. `pyramid` is the main web application. when a user uploads a file, it is handed off to `celery` via `redis`, which handles all the image resizing and uploading onto S3. the solution we went with: • short polling on a configurable delay. We default to 2500ms, and

Re: [pylons-discuss] Re: advice for sending events back to javascript from pyramid (redis, polling, asyc, etc)

Thanks Jonathan, your solution is what I was leaning to for proof-of-concept, good to know it's somewhat performant too. I don't know enough about fast response time situations to really know the pros and cons of short-polling, long-polling, and websockets. Did you also look into erlang at all? I

Re: [pylons-discuss] Re: advice for sending events back to javascript from pyramid (redis, polling, asyc, etc)

Thanks everyone. To clarify for Jonathan, we're using RabbitMQ as our bus for jobs between web services and worker processes, while I'm thinking Redis as a fast way to get messages back to client apps, mostly because the cost of a request checking Redis is so low. I could see our use of RabbitMQ

Re: [pylons-discuss] Re: advice for sending events back to javascript from pyramid (redis, polling, asyc, etc)

Do any of you have any experience using cyclone for handling the redis-to-client side of things? iain On Tue, Sep 29, 2015 at 5:32 PM, Iain Duncan wrote: > Thanks everyone. To clarify for Jonathan, we're using RabbitMQ as our bus > for jobs between web services and