- From: Ted Goddard <ted.goddard@icesoft.com>
- Date: Thu, 2 Nov 2006 09:04:13 -0700
On 2-Nov-06, at 5:05 AM, Dave Raggett wrote: > well how about an XMLBEEPRequest specification then? > > Beep is kind of like a bidirectional version of HTTP and includes > multiplexing capabilities with stream prioritization, see: > > http://beepcore.org/index.html > > Beep isn't in widespread use as yet, but is well thought off > by the IETF folks. This would require the standardization of a JavaScript API for BEEP, but it would be worthwhile because BEEP is explicitly designed for building new protocols. BEEP messaging would probably map better into JavaScript than a pure socket API. (Would we want to insist that the payload be XML?) Of course, it wouldn't work if it was only implemented in the ICEbrowser ... (so I'm curious what other browser developers think of the idea) Regards, Ted. > Dave Raggett <dsr at w3.org> http://www.w3.org/People/Raggett >
Received on Thursday, 2 November 2006 08:04:13 UTC