users
[Top] [All Lists]

Re: [cinjug-users] Messaging At the Web Layer

To: esumerfd@xxxxxxxxxxxxxx
Subject: Re: [cinjug-users] Messaging At the Web Layer
From: "Paul Spencer" <spencepd@xxxxxxxxx>
Date: Tue, 23 Oct 2007 15:51:26 -0400
Cc: CinJug <users@xxxxxxxxxx>
Delivered-to: mailing list users@xxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=odIxVoPUnB+NI8+fliAjs1eBOl7UOTYA130kdrF2tKY=; b=Nr4hIxbz8rkzCq+mxwyx+YtQRU3uUf6US30K4C7NdKkf3f9Uw03WEwO5bsmt2Uzmc+VIWKBKzfkQK9uBGiQbwi2TnLEVq5ESaLTjWavm1fNGunJY8tM2OAq6TbolJ0Vddl70hkOOguD1etCVOthMgLyZnWBvQLVP/2fpzKXu3xo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=kMqHbrIiJSYiZRCwBDicAvcMbPsUHCUbi8jwdWpdkAajbYP7gILyouaewOuUpUwfQpkjvidFO9U3KFGVd+MA8L7xfyGOzAyTLfUKfYJucDtIICBVRQmwXG4xfd50hd/0EAVjc+TaVvhM+FT65kW1cCrPrsk/tHlXrMccOZ4s1cM=
In-reply-to: <6a216ba20710231235h730074f7ma164455e7bb8307a@xxxxxxxxxxxxxx>
Mailing-list: contact users-help@xxxxxxxxxx; run by ezmlm
References: <6a216ba20710231235h730074f7ma164455e7bb8307a@xxxxxxxxxxxxxx>
How about some kind of polling using AJAX?  Maybe the web layer can look for a message update on the server.  Not exactly sure what the implementation would look like, but I think it could work.

Found this.

http://windyroad.org/2006/07/25/event-driven-ajax-part-1-pushing-server-side-events/

On 10/23/07, Edward Sumerfield < esumerfd@xxxxxxxxxxxxxx> wrote:
I am considering implementing a JMS messaging container at the Web layer. Tell me I am a fool? :-)

I have a simple web app polled by a client every second for its data. Not wanting to hit the database for every client, every second, it is cached at the web layer.

Enter JMS. We will be receiving notifications of changes to the database data via JMS messages. So MessageDrivenBeans, deployed to JBoss EJB container will receive these messages but what should they do to tell the cache in the Web container to update.

It seems my options are to push the cache to a java space somewhere so that the web layer and the MDB's can access it or to move the messaging container to the web layer.

Thoughts?

Ed


<Prev in Thread] Current Thread [Next in Thread>