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
{{ message }}
This repository was archived by the owner on Jun 19, 2018. It is now read-only.
Jetty9 allows control over this and it was overlooked on first releases, let's fix this!
The main idea is that acknowledged puts indicate succes delivery in write mode, and in read we wont feed the input channel until reads from it. That means that a user who checks return values of operations on a channel will be able to do proper flow control, otherwise he'll be bound by the kind of buffer used (if any provided other than the default) and/or the internal core.async put queue size. This should satisfy everybody, as you can work in sync or write faster than delivery if you dont' care (you should care).
Jetty9 allows control over this and it was overlooked on first releases, let's fix this!
The main idea is that acknowledged puts indicate succes delivery in write mode, and in read we wont feed the input channel until reads from it. That means that a user who checks return values of operations on a channel will be able to do proper flow control, otherwise he'll be bound by the kind of buffer used (if any provided other than the default) and/or the internal core.async put queue size. This should satisfy everybody, as you can work in sync or write faster than delivery if you dont' care (you should care).
websocket
http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/websocket/api/Session.html#suspend()
http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/websocket/api/SuspendToken.html
server
http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/server/HttpOutput.html
http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/server/HttpInput.html
http client
The text was updated successfully, but these errors were encountered: