Prompted by: >Basically, I've never seen this particular approach before so I'm >questioning its practicality. <snip> > I could be convinced otherwise, though, especially if it is some > standard that I just don't know about :)
I did some more googling, looking for references re applications and standards covering bi directional communication between browser and backend. In a discusion[1] of the TCPConnection object in the "Web Applications 1.0 Working Draft — 18 November 2005" from www.whatwg.org. I came accross accross this comment: > All the current implementations of that are huge > hacks that would be much simpler to implement if they could just open a > TCP connection and send free-form data back and forth. --- http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2005-October/004886.html And thought that sounded painfully close to dispatch.js alright. Also encountered rfc 3080, 3081, and BEEP for the first time: http://www.ietf.org/rfc/rfc3080.txt http://www.xml.com/pub/a/2002/10/16/ends.html http://www-128.ibm.com/developerworks/webservices/library/x-beep/ My interest in all of this is from the "casual online games" perspective. And with the requirement that the user experience span more than one device: mobile phone + PC based web browser. So I'm quite encouraged by the TCPConnection, and PeerToPeerConnections, mentioned in sections 6.3.4 & 6.3.6.1 of the "web applications" draft. A javascript take on this is http://jsbeep.mozdev.org/ but it looks like its gone cold. Anyways, thanks to all for the feedback. Cheers, Robin
