> 1) a bosh session was issued per browser session and not per opened tab i.e. > a single "sid" across all open tabs > 2) when bosh session is first issued, an attribute named "tabid" is also > provided to the connecting browse tab. > client will use this "tabid" (issued by the bosh CM) along with "rid" > for all bosh requests > 3) when a new tab opens up, client connects to existing bosh session for the > current browser session, > server simply issues a new "tabid", every open tab have their own > sequence of "rid"
This doesn't help you much because without knowledge about what the other tabs are doing, there's no way to maintain state across tabs. The shared bosh stuff that I proposed had a way to subscribe to the traffic of the your shared peers so that you could make state changes based on what they were doing. I suppose you could echo everything each tab sends, but that might get unwieldy. The real solution is to use shared web workers, but sadly, these aren't well supported (if at all) yet. Then you'd have a central worker maintaining all the state and bosh connection stuff, and all the tabs would just communicate with it. jack.
