Home/ Questions/Q 7986279
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T11:48:42+00:00

for a django application I’m working on, I need to implement a two ways

  • 0

for a django application I’m working on, I need to implement a two ways RPC so :

  • the clients can call RPC methods from the platform and
  • the platform can call RPC methods from each client.

As the clients will mostly be behind NATs (which means no public IPs, and unpredictable weird firewalling policies), the platform to client way has to be initiated by the client.

I have a pretty good idea on how I can write this from scratch, I also think I can work something out of the publisher/subscriber model of twisted, but I’ve learned that there is always a best way to do it in python.

So I’m wondering what would be the best way to do it, that would also integrate the best to django. The code will have to be able to scope with hundreds of clients in short term, and (we hope) with thousands of clients in medium/long term.

So what library/implementation would you advice me to use ?
I’m mostly looking to starting points for RTFM !

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    websocket is a moving target, with new specifications from time to time. Brave developpers implements server side library, but few implements client side. The client for web socket is a web browser.

    websocket is not the only way for a server to talk to a client, event source is a simple and pragmatic way to push information to a client. It’s just a never ending page. Twitter fire hose use this tricks before its specification. The client open a http connection and waits for event. The connection is kept open, and reopen if there is some troubles (connection cut, something like that).
    No timeout, you can send many events in one connection.

    The difference between websocket and eventsource is simple. Websocket is bidirectionnal and hard to implement. Eventsource is unidirectionnal and simple to implement, both client and server side.

    You can use eventsource as a zombie controller. Each client connects and reconnect to the master and wait for instruction. When instruction is received, the zombie acts and if needed can talk to its master, with a classical http connection, targeting the django app.

    Eventsource keep the connection open, so you need an async server, like tornado. Django need a sync server, so, you need both, with a dispatcher, like nginx. Django or a cron like action talks to the async server, wich talks to the right zombie. Zombie talks to django, so, the async server doesn’t need any peristance, it’s just a hub with plugged zombies.

    Gevent is able to handle such http server but there is no decent doc and examples for this point. It’s a shame. I want a car, you give me a screw.

    • 0