I know the browser only handles 2 open connections to one server, and I've read the server-push FAQ. The design of the app calls for having 4-5 section/windows/sections/frames (whatever you want to call them), which I was either going to have each in it's own separate module (running the same browser) or in one module, currently this is undecided. Each section needs it's own data from a database. Ideally, the simplest way would be to have each section have it's own hanging/waiting request for data, but the 2 connection limit stops that plan. It there a framework out there that handles multiplexing of some sort. I've read a bunch on comet and cometd, but I'm unsure if this is a solution.
The other option would be for me to code the multiplexing. Have one open request that kind of asks the server "do we have ANY data for ANY section ready?" and then return that and have the callback sort it out and figure out where it needs to go. I'd rather not do it that way in case we end up having variants of the app or other apps that may use one of the sections or it. Any insights on this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
