Re: [jetty-dev] Refactored WebSocket API

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

Are you planning on having an OnExtention callback that can use the
api user the block of data associated with that extension and whatever
metadata is known about it?

That might conflict or duplicate with the onFrame but perhaps as a
option, following frames vs following extensions..  At least from my
limited understanding the extension as an abstraction seems more
interesting then the frames that might be involved with it getting
that extension from point a to b.

cheers,
jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Thu, Mar 10, 2011 at 07:56, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:
> All,
>
> due to changes in the draft-06 (and soon to arrive draft-7) websocket
> specification, I've had to significantly refactor the WebSocket API.
>
>   http://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk/jetty-websocket/src/main/java/org/eclipse/jetty/websocket/WebSocket.java
>
> The intent is to have nested interfaces for OnTextMessage,
> OnBinaryMessage, OnControl and OnFrame to contain callbacks for
> different types of message.  The first three are called back with
> complete aggregated messages, while the OnFrame is called with all
> frames, which may be message fragments.
>
> The Outbound subinterface has also been renamed Connection, as it now
> provides more info about the inbound side (eg protocol, and maximum
> size of aggregated messages).
>
> This is just in SVN for now and it is not set in stone.   So feed back
> and ideas are very welcome.
>
>
> cheers
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>