Re: Questions about Comet Session Protocol
10 views
Skip to first unread message
Michael Carter
Oct 27, 2009, 3:56:39 AM10/27/09
to Andrew Rondeau, js...@googlegroups.com
On Mon, Oct 26, 2009 at 12:50 PM, Andrew Rondeau <a...@andrewrondeau.com> wrote:
Yes, the jsio google group; you can sign up here: http://groups.google.com/group/jsio
I've also cc'ed the list my reply, so we can continue there.
Yes. Some tranports split packets up.
This is acceptable, but you'll eat up your connection limits fast with older browsers, even using wildcard dns. In general, its best to multiplex on top of CSP -- this is what Orbited 0.8 does. It offers a higher level api called TCPSocket. Each time you instantiate a TCPSocket, it uses the existing CSP connection (if none exist, a new one is created.)
This is fine up until you hit the persistent connection limit in the browser. With wildcard dns enabled, this is 8 in IE6, (or maybe 6?) and much higher in all other browsers. This will probably not cause trouble until you have 32 tabs with a csp connection in all of them.
-Michael Carter
Hi Mike,
I just read through the Comet Session Protocol spec. It seems like you've pretty much ironed out the different kinds of transport issues that can occur, and worked them into the protocol.
I do have some questions:
1: Is there an online forum that we can ask/answer questions so our conversation stays open?
Yes, the jsio google group; you can sign up here: http://groups.google.com/group/jsio
I've also cc'ed the list my reply, so we can continue there.
2: It looks like an application's packets can be broken / merged, just like TCP sockets:
2a: Assuming my in-browser application sends two packets, "ABC" and "DEF", can the server application possibly get an "ABCDEF" packet?
Yes. Some tranports split packets up.
2b: Assuming my in-browser application sends one packet, "ABCDEF", can the server application possibly get two packets, "ABC" and "DEF"?
Yes, all transports attempt to merge packets where possible
3: What happens if a page opens multiple Comet Sessions at the same time?
This is acceptable, but you'll eat up your connection limits fast with older browsers, even using wildcard dns. In general, its best to multiplex on top of CSP -- this is what Orbited 0.8 does. It offers a higher level api called TCPSocket. Each time you instantiate a TCPSocket, it uses the existing CSP connection (if none exist, a new one is created.)
4: What happens if the user opens multiple tabs / windows, and each tab/window opens one Comet Sessions?
This is fine up until you hit the persistent connection limit in the browser. With wildcard dns enabled, this is 8 in IE6, (or maybe 6?) and much higher in all other browsers. This will probably not cause trouble until you have 32 tabs with a csp connection in all of them.
-Michael Carter
- Andy
GWBasic
Oct 27, 2009, 4:03:36 AM10/27/09
to js.io
Cool, thanks.
So assuming that I'm multiplexing, is there a recommended URL and
convention to expose for multiplexing?
So assuming that I'm multiplexing, is there a recommended URL and
convention to expose for multiplexing?
Michael Carter
Oct 27, 2009, 4:11:51 AM10/27/09
to js...@googlegroups.com
On Tue, Oct 27, 2009 at 1:03 AM, GWBasic <goo...@andrewrondeau.com> wrote:
Cool, thanks.
So assuming that I'm multiplexing, is there a recommended URL and
convention to expose for multiplexing?
Jacob Rus has written a specification which both js.io and Orbited uses for multiplexing. I'm not sure where it is though, do you have a link Jacob?
Reply all
Reply to author
Forward
0 new messages