holding the cnxn open is SUCH a cool idea, Folke! {and kilkenny, who i
notice just posted useful links}
whoever thought of that is a crafty person to trick http like that.

however, it slows me down considerably, presumably because of the
large number of other rpc calls my app makes {in parallel}.
i hate the 2 call per server limit- maybe i can make a separate
realtime server?

1) can i actually make a separate server to handle realtime stuff, or
does the same origin policy make an unsurmountable wall?
2) would doing that solve my problem, or does hanging a connection on
a coat hook eat resources in some other way than just queuing
simultaneous http cnxns?

thx, elliot

On Sep 4, 2:03 am, kilkenny <[EMAIL PROTECTED]> wrote:
> Hi Eggsy
>
> Check out these 
> links:http://code.google.com/p/google-web-toolkit-incubator/wiki/ServerPushFAQhttp://docs.codehaus.org/display/JETTY/GWT
>
> Hope that helps.
> Adrian
> --http://traceurl.com
>
> On 3 Sep., 22:05, eggsy84 <[EMAIL PROTECTED]> wrote:
>
> > Hi all
>
> > I'm just writing to see (may have already been discussed) if anyone
> > has used GWT Client/Server communication in a way that the server
> > notifies the client?
>
> > At times when developing applications I have found myself thinking it
> > would be much easier if the server could simply notify the client(s)
> > of a state change?
>
> > Typically GWT works by Async calling the server which is completely
> > fine but I was wondering if this can be flipped such as new services
> > like MobileMe profess to do - pushing contact to a client!
>
> > Just wondering if anyone has done this?! How did they apporach it?
>
> > Eggsy
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to