I've been working on a comet like thing for an application that uses pop-up windows. Along the way I've run into some very tough puzzles about how to maintain just one open connection. <br><br>Basically the problem is (as I see it) that for comet to work well it needs to have only one connection. My tests show that only one window can have that connection or they clobber each other. So the plan is to have one window be the only opener for the pop-ups and that the pop-ups would be fed data from the opener. But what if the opener refreshes, closes or goes to another URL? Also, what if the opener URL is opened in another window? If the opener is refreshed, the child windows can re-register themselves in the opener. If the opener closes or goes to another URL, though, I don't see any good way to manage the comet connection. And if the opener is opened in two windows, is there any reliable way to determine which gets the comet connection?
<br><br>I think the "real" solution for this is to have the browsers support a connection pool accessable via javascript with IDs or something. Oh well. ... So far, the only "reality-based" solution I can think of is to just use regular ajax polling. But what do I know?
<br><br>Does dojo's io package offer anything to help with this stuff? I haven't been using dojo's io package so far so pardon my ignorance please.<br><br>???<br>,chris<br>