On Mon, 17 Dec 2018, Prashant Shubham wrote:
If you want the client to get the data as soon as it gets available then you should probably just make a request with curl and not have a timeout. Then curl will just sit there waiting for the transfer to start or complete, until the server does that. And when one transfer is done, the client can just issue another request and go back to waiting...
But meanwhile when we client is issuing another request what if server has to send another new command to client, wouldn't the client miss that command?
If the server can't cache the data for a while then I would say uysing HTTP for this setup seems wrong.
-- / daniel.haxx.se ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
