The AMQ idea looks like an interesting one I wonder if anyone has
implemented this through GWT.
On Sep 5, 6:07 am, elliot <[EMAIL PROTECTED]> wrote:
> their impl is rather like the one thomas described, using a comet-like
> open cnxn coupled with a timeout.
>
> '
> To avoid the load vs late
their impl is rather like the one thomas described, using a comet-like
open cnxn coupled with a timeout.
'
To avoid the load vs latency tradeoff, AMQ uses a waiting poll
mechanism. As soon as the amq.js script is loaded, the client begins
polling the server for available messages. A poll request
I wonder if anyone has tried Active MQ. They seem to have a javascript
client for JMS
http://activemq.apache.org/ajax.html
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to thi
Thanks for the response.
> Another solution: make your RPC calls only "accept" (in the sense of
> the 202 HTTP status code) the request and send the response back into
> the "comet feed". That way, your RPC calls would be very fast (the
> server answers without any processing) and could be queued
Thanks for the response.
> Another solution: make your RPC calls only "accept" (in the sense of
> the 202 HTTP status code) the request and send the response back into
> the "comet feed". That way, your RPC calls would be very fast (the
> server answers without any processing) and could be queued
On 4 sep, 08:51, elliot <[EMAIL PROTECTED]> wrote:
> 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 th
Brilliant feedback guys!
GWT group always helps each other!
Thank you will check over the links now
---
On Sep 4, 7:51 am, elliot <[EMAIL PROTECTED]> wrote:
> 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
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}.
Hi Eggsy
Check out these links:
http://code.google.com/p/google-web-toolkit-incubator/wiki/ServerPushFAQ
http://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
You can make the server hold the connection open until something needs
to be send to the client.
http://en.wikipedia.org/wiki/Comet_(programming)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" gr
the only way i know of to accomplish this is to use a heartbeat.
every 5s or so, fetch all important notifications from the server.
process them in the client, possibly making more calls to do so.
i cant imagine that there exists a secure way to trigger events
directly from afar.
On Sep 3, 4:05
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 clien
12 matches
Mail list logo
