i've been looking at the v2 examples. the inclusion of encoder/decoders
already honors application level extensions. but i am wondering if this
mechanism shouldn't be centered around the concept of web socket
subprotocols instead.
IMO a client requesting a certain subprotcol will implicitly refer to
a set of encoders/decoders associated with the protocol.
i cannot foresee all the implications it has on the API, cut certainly
the client#connect and server#registerEndpoint API's would need to
represent the notion of subprotocols somehow...
regards, heiko