We do something like this to create a "cookie crumb trail" through our
application. Ours isn't a complete history, but instead a Stack that is
truncated whenever the user re-visits a page already in the list. Anyway,
we basically just keep a Stack variable with the request URIs in a session
attribute, as you suggest.
-Christopher
|---------+---------------------------->
| | "Craig |
| | Christophersen" |
| | <[EMAIL PROTECTED]|
| | .com> |
| | |
| | 06/23/2004 05:04 |
| | PM |
| | Please respond to|
| | users |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------|
|
|
| To: <[EMAIL PROTECTED]>
|
| cc:
|
| Subject: Users history for session
|
>--------------------------------------------------------------------------------------------------------------|
I am tasked with making a way for a user to bring up a history of their use
for a session such that they can link from it to any document they have
viewed. Any direction on how to accomplish this? I cannot use cookies.
Should I store each request uri as a session attribute?
Craig Christophersen
(406)496-6421
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
