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 can be sent
as a GET request or as a POST if there are other messages ready to be
delivered from the client to the server. When the
MessageListenerServlet receives a poll it:
1. if the poll request is a POST, all send, listen and unlisten
messages are processed
2. if there are no messages available for the client on any of the
subscribed channels or topic, the servlet suspends the request
handling until:
* A MessageAvailableConsumer Listener is called to indicate
that a message is now available; or
* A timeout expires (normally around 30 seconds, which is
less than all common TCP/IP, proxy and browser timeouts).
3. A HTTP response is returned to the client containing all
available messages encapsulated as text/xml.
'
On Sep 4, 9:45 pm, Ron Lawrence <[EMAIL PROTECTED]> wrote:
> 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 this group, send email to Google-Web-Toolkit@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
