Their Comet system is broken because they are using the same domain. So when you hit the maximum simultaneous connections, your browser will refuse to load you any single page/content from finance.google.com anymore, pretty silly.
You sure they're not just using a smart request bus to multiplex those connections? If you've actually seen it break then fair enough, but I'd be surprised if they hadn't accounted for that issue.
It's one connection per page, open 8 pages in Firefox (2.**) and then try opening another one. You can multiplex connection inside a same page yes, the golden rule is to not consume more than 2 at the same time. But there are no mechanism to do that across frames, tabs, windows.
Their Comet system is broken because they are using the same domain. So when you hit the maximum simultaneous connections, your browser will refuse to load you any single page/content from finance.google.com anymore, pretty silly.
Bayeux document has a little explaination on that issue: http://svn.cometd.com/trunk/bayeux/bayeux.html#toc _77
Facebook chat handles this pretty well with sub-domains that get incremented: 0, 1, 2, 3, ... for each new tab/window/frame open.
You sure they're not just using a smart request bus to multiplex those connections? If you've actually seen it break then fair enough, but I'd be surprised if they hadn't accounted for that issue.
anon - 4th June 2008 13:34 - #
It's one connection per page, open 8 pages in Firefox (2.**) and then try opening another one. You can multiplex connection inside a same page yes, the golden rule is to not consume more than 2 at the same time. But there are no mechanism to do that across frames, tabs, windows.
It surprized me as well.