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

[Chris Nelson <cnelson4eii@xxxxxxxxx>]

Were you there the night we had terracotta in?  Off the top of my head it sounds like it might be a decent fit for what you are doing.  You could use it (I think) to create a cache both JMS and the web could share.

--Chris

----- Original Message ----
From: Edward Sumerfield <esumerfd@xxxxxxxxxxxxxx>
To: CinJug <users@xxxxxxxxxx>
Sent: Tuesday, October 23, 2007 3:35:36 PM
Subject: [cinjug-users] Messaging At the Web Layer

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

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com