Christopher Zhao wrote:
> All-
>
> To do:
> 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. You can get around the URL length problem by using POST instead of
GET (and using hidden fields for the current values), but you are still sending a
LOT of bytes back and forth that the client browser really does not care about.
>
> Tahnks.
>
> Chris zhao
>
Craig McClanahan
___________________________________________________________________________
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
