Hello, I am building an application that will store menu options in a database. These menu options will display on every page in the application. I am interested in finding the most efficient way of doing this. My options as I see them are: 1. provide a base action for the entire site (similar to struts-mailreader) that will provide me with a method to load the menu information and store it in the request. This option is heavy on database traffic. 2. still use the base action but store the information in the session when the user first visits the site. This option is an awkward type of cache that might behave strangely with high volume to the site. 3. load the menu options one time from the database and place in the application scope. While this is the best memory option (and probably the most efficient for speed), I'm not sure how I would reload this after a change was made to the underlying database (or even detect that a change was made).
I suppose that there is a final option which would be to use a chaching layer between for database transactions and go with option 1. Is a base action the best approach? thanks in advance for your comments. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
