Craig R. McClanahan <[EMAIL PROTECTED]> wrote:
>Christopher Zhao wrote:
>> For one servlet, I have many layers of presentation classes. Users can
browse
>> the service through a function nevigation bar. The navigation bar is
created on
>> the fly so that functions on the bar can remember user's activity through
>> parameter passing.
>>
>> Problem:
>> When layer's information is passed, the parameters will be to long for
URL. If
>> If I use decoded parameter passing, the string could be even longer.
>>
>> Question:
>> What is a good strategy to implement this.
>>
>
>I would suggest keeping all of the "state" information about available
options (the
>stuff needed to create your navigation bar) in a session, rather than
passing it
>back and forth.
If the user opens a new window using certain browsers, the new window will
be part of the same session. If the navigation information is kept in a
session, then moving around in one window can mess up the navigation of the
other window.
A good way to get around the problems with sessions and multiple browser
windows is to "join" any sessions created by the same user (if the user is
known). This can be good for things like shopping carts, but horrible for
navigation.
Does someone have a suggestion for getting around the multiple browser
window problem when using sessions for something like navigation?
Erik
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
