Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <10360381.post@talk.nabble.com>
Date: Mon, 7 May 2007 09:16:27 -0700 (PDT)
From: northshorefiend <spam123@JamesAshepherd.com>
To: users@activemq.apache.org
Subject: Javascript -> JmsReplyTo(TemporaryDestination) -> JSONP
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Say you have a widget on a webpage. The user clicks 'send' and expects a
'synchronous' response.

You could just register a listener with amq.js and wait asynchronously for a
reply.

But the user complains it is not fast enough.

So what about using the JSONP idea to contact the server outside of the GET
poll and the POST batch sending that amq.js does?

On the server side I expect a Servlet would be needed that forwarded the
message and waited for a reply using a TemporaryDestination then do the
JSONP thing.

I think this would entail a split in the taxonomy of widgets: a widget that
uses the above style could not also be updated via AJAX polling, as I
believe the AJAX response could be queued in the server side whilst a JSONP
response updates the widget. When the AJAX response returns it would contain
stale data.

I suppose it is a bit subversive.

I have another idea, but I can't make a link to a future post here :-)
-- 
View this message in context: http://www.nabble.com/Javascript--%3E-JmsReplyTo%28TemporaryDestination%29--%3E-JSONP-tf3704747s2354.html#a10360381
Sent from the ActiveMQ - User mailing list archive at Nabble.com.