I was just looking at
For some simple stand alone scripts I’d like to use long polling for simple applications,
that subsribe and wait for a callback. websocket, twisted (or asyncio) seem to be a little overkill and I’d like to keep the script tiny.
Further I’m still having a small issue with a small asyncio snippet (don’t know how to stop the loop), which I will address in a separate
However apart from the fact, that I don’t understand the curl example completely I have the impression, that the example is not complete:
The example seems to try to explain following
1.) 1 POST request to open a connection
2.) 1 POST request to subscribe (this one is missing in the doc)
3.) 1 POST? request for long polling
4.) repeat three until no more listening is required
5.) 1 POST request to close the connection when finished
So my first question:
1.) what is the exact request for subscription?
2.) what is the exact rule of the debug_transport_id
2.a) is there any issue leaving a fixed debug_transport_id in a production environment
2.b) how would the ‘curl’ example look like if the transport_id would NOT be hard coded.