Pieter Hintjens wrote:
> I'd like to see this WebSocket vs. BWTP discussion end, and the energy
> going into prototype code, use case documentation, and community.
Definitely.
But just for the record (and in regard to your point about "alternative" in
other thread), I don't think I've ever thought of this as "WebSocket vs BWTP"
BWTP is currently a thought experiment with lots of possible out comes:
a) ideas from BWTP (or elsewhere) get incorporated into websocket.
b) BWTP (or something like it) get's built on top of websocket
c) BWTP (or something like it) evolves into a real protocol solving
different problems than websocket.
d) Some other effort proves to be a better vehicle for a)-c) (maybe waka?)
e) There is no significant interest and BWTP fades away.
I guess I've been hammering on a) a bit too much - my apologies.
cheers
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.