]
Sent: Saturday, December 21, 2002 4:55 AM
Subject: RE: [JSTL] Help hiding/showing sections on JSP (w/ cookie?)
On Fri, 20 Dec 2002, Wendy Smoak wrote:
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
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.
Doing something along these lines would not only reduce the load on
On Fri, 20 Dec 2002, Wendy Smoak wrote:
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.
Doing something along
I have a JSP with several sections, each of which needs to be hidden or
shown based on user preference. I believe I've gotten the code done to
toggle the on/off value of each section and to set a persistent cookie for
the user in the form of: profile_sections = YYYNNNYYYNYNYNYYNN
Now I'm
On Thu, 19 Dec 2002, Wendy Smoak wrote:
x:if select={$showAddress}
tabletrtdstuff/td/tr/table
/x:if
Or can I get at the cookie with JSTL? (And pick out a specific position of
it??) The setting of the cookie is done in a Struts Action, so I've got
Struts (and Struts-EL) tags
Shawn Bayern wrote:
On Thu, 19 Dec 2002, Wendy Smoak wrote:
x:if select={$showAddress}
tabletrtdstuff/td/tr/table
/x:if
Or can I get at the cookie with JSTL? (And pick out a specific position of
it??) The setting of the cookie is done in a Struts Action, so I've got
Struts (and
Glass houses, stones, and all, but I think it's a yicky solution, far
too dependent on nothing ever changing :) If I were doing it I'd explore
other options (storing user prefs in a db indexed by a cookie value, for
instance) and work off of that. Having position-dependent values seems
an
Shawn Bayern wrote:
Oh, I definitely agree. Personally, I might just set multiple cookies,
unless there were more than perhaps a dozen of them.
That was my first thought too, but as I choose to confirm every cookie I
get I discourage people from using them ;)
Dave
--
To unsubscribe,
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
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 0010001000 or
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
11 matches
Mail list logo
