I may
have problem in using this idea. We use iPlanet webservers. One webserver has
several app server instances in a load balance. Which means that hitting
one JSP page to refresh the cache will only refresh one of three app server
instances.
--------Original Message-----
From: Greg Nudelman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2003 3:05 PM
To: jdjlist
Subject: [jdjlist] RE: Caching of semi-static data across webappsI like the idea, but you'll still have the problem of hitting each of the 20 machines with the GET/POST. Unless you go to the localhost of each machine (a hassle), you can not be sure you will reach all of the 20.I guess you can write a script to hit each of the machines by its specific internal IP from within the firewall.Greg--------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
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
http://www.sys-con.com/fusetalk
