True. But I think it is better than having 20 machines polling an application server/database every 5 minutes (or whatever interval). Though, obviously this depends on the immediacy required. If it needs to be within 5 minutes then I think my suggestion has merit. But if it just needs to be updated in the next 24 hours then polling would be better. As it is, the webserver/servlet container needs to know the local IP address so that it can bind to the address.
Paul Franz
----- Original Message -----
From: Greg Nudelman <[EMAIL PROTECTED]>
Date: Wed, 5 Mar 2003 12:05:01 -0800
To: "jdjlist" <[EMAIL PROTECTED]>
Subject: [jdjlist] RE: Caching of semi-static data across webapps
--------Original Message-----
From: Paul Franz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2003 7:38 PM
To: jdjlist
Subject: [jdjlist] RE: Caching of semi-static data across webappsOne thing that I don't think people have thought of. How about a light/poor mans JMS implementation. In this case, the webserver that gets triggered to reload the translations notifies the other webservers via a GET/POST request to a special servlet. Yes, this means that setup is a little more complicated but it avoids the extra traffic of polling the app server. Heck, if you want to you can have the webservers register with the app server by add records to the database of the IP address of the webserver.
Paul Franz
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
http://www.sys-con.com/fusetalk --
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
Meet Singles
