Strange behaviour about django-eventstream HOT 7 OPEN

Hi,

The processes don't talk to each other, so when a message is sent it is only pushed to clients connected to the same process. To support multiple processes, you'll need to delegate connection management to a GRIP proxy. See multiple instances and scaling.

If you don't expect tons of traffic, I'd say just use 1 Daphne process.

from django-eventstream.

Hello,

Thanks for your answer. In a first time, i try to use pushpin, butdid not success to make it works on my mac. (message sent to pushpin, bud did not déliver). I will give it a try again.

If you get any tips, you're wellcome :-).

Thanks for all.

from django-eventstream.

Hey @tboulogne,

A few items to consider:

1. Make sure your GRIP_URL points to the Pushpin HTTP Control API.

# default local Pushpin HTTP Control API
GRIP_URL = 'http://localhost:5561'

2. Make sure your Pushpin configuration has the proper route setup in the routesfile.

* http://localhost:8000

Replace localhost:8000 with whatever your app's <host>:<port> combination is.

3. Make sure that when you're accessing your site, you're doing so through the Pushpin URL and not the app URL. By default, Pushpin will listen at http://localhost:7999.

Let us know if you have any additional questions!

from django-eventstream.

hey @kevinswiber,

Thanks for insights.

Point 3 mean, that the upstream backend for nginx is pushpin and not daphne ?

from django-eventstream.

@kevinswiber i got a working pushpin :-) !

Bu if face randomly lost connection on some statics files :

Any tips to improve this please ?

Thanks for all.

Regards

from django-eventstream.

Weird. Is this easy to reproduce? Can you share the logs from pushpin-proxy.log around the time this happens?

from django-eventstream.

hello,

Sorry for the delay. As i need to progress on this project, i switch back to one instance. But i will take some time and back to you with details.

Could hold this case for now if you want.

Regards.

from django-eventstream.