I've heard tell of folks serializing things such as this. If you're not in a distributed environment (or you somehow manage to have a shared directory available to all nodes of the "cluser") you could probably do the same. Just either serialize them through the typical means or by using one of the new XML strategies. You could then implement a proxy for getting settings belonging to a given user which could easily be accessed via the JSTL.

Doing something along these lines would not only reduce the load on the DB, but enable the user the priviledge of having the same settings on every machine they visited the site from.

Wendy Smoak wrote:

Oh, I definitely agree. Personally, I might just set multiple cookies,
unless there were more than perhaps a dozen of them.

Unfortunately, there are already a dozen, and although we resist adding more
sections to that page, I have a handful of requests, one or two of which
will probably make it.  I thought that was too many to set individual
cookies. :(

So I'd like to set one cookie, the format of which is open to suggestion,
read it in a Struts Action, do whatever with the value, and then use some
JSTL tags to decide whether or not to display a given section.

Having never done anything of the sort before, either 00100010111100 or
YYYNNNYYNYNY came to mind.  (And an evil coworker suggested turning the
first into a decimal number before setting the cookie.)

--
Eddie Bush




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to