[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-dev] jetty-9 websockets API
|
so still on my wish list are methods like:
// to have jetty stop trying to deliver frames to the app..
WebSocketConnection.suspendReads()
// to resume receiving frames
WebSocketConnection.resumeReads()
and yes I hope those write methods with callback would be non-blocking. Jetty should internally buffer the writes if the socket is not accepting more data. In other words, the caller should do it's own flow control.
On Tue, Jul 3, 2012 at 7:03 AM, Greg Wilkins
<gregw@xxxxxxxxxxx> wrote:
Jesse/Joakime
I've moved this to jetty-dev where it should be.
I had a quick look at the proposed standard websocket API.... it does
not shout "I'm wonderful" at me. However the interesting thing is
the feedback from others - there appears to be support for using
streams to send/receive large messages independently from frame
boundaries. We should also look at it more closely to see if we can
get at least convergence on naming etc.
--
Hiram Chirino
Software Fellow | FuseSource Corp.
chirino@xxxxxxxxxxxxxx | fusesource.com
skype: hiramchirino | twitter: @hiramchirino
blog: Hiram Chirino's Bit Mojo
![]()
