You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To save on server-load renegotiating several SSL connections it might be interesting to implement server-sent events as means of returning the status. That way, only one connection has to be opened by the client, which reduces load on the server.
Default reporting interval might be 1000ms or 1 MiB, whatever happens first. Optional reporting details via request, e.g. /report?upload_id=foo&interval=750&block=524288 for updates every 750ms or completion of 512KiB.
The text was updated successfully, but these errors were encountered:
To save on server-load renegotiating several SSL connections it might be interesting to implement server-sent events as means of returning the status. That way, only one connection has to be opened by the client, which reduces load on the server.
More information on Server-Sent Events can be found at the W3C at https://www.w3.org/TR/2009/WD-eventsource-20091029/
Default reporting interval might be 1000ms or 1 MiB, whatever happens first. Optional reporting details via request, e.g. /report?upload_id=foo&interval=750&block=524288 for updates every 750ms or completion of 512KiB.
The text was updated successfully, but these errors were encountered: