Four times a YEAR? If that is the case, I would store the data in property files. That way if a new version of JRun comes out, you don't have to remember to reset the variables in the configuration file or JMC.
For commonly-accessed lookup data that is fairly static, I would cache the static data per the instructions in the JRun Programmer's Guide (Optimization chapter): http://livedocs.macromedia.com/jrun4docs/Programmers_Guide/servletoptimizing2.jsp and http://livedocs.macromedia.com/jrun4docs/Programmers_Guide/servletoptimizing3.jsp Or check Drew Falkman's book "Web Application Construction Kit". He discusses this with code examples for JRun and he is an active member of this list. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 7:48 PM To: JRun-Talk Subject: application variables I have some data that I would like to have available to all users, the data is updated each four times a year at the most. Would storing them as application variables be the best choice? Data is currently stored in the db. Also, I have other type of data, such as lookups, that are not rarely updated (like list of countries, sectors etc...). What would be the best type of storage? In order to access them (for editing, search pages etc...) Thanks, ______________________________________________________________________ Get the JRun Web Application Construction Kit - the only book written specifically for JRun developers. http://www.amazon.com/exec/obidos/ASIN/0789726009/houseoffusion Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
