Hi,
I'm not sure what do you mean by a cleaner approach. But, I can suggest
you an alternative. You could try to put you're tracking information in
the HttpSession object rather than putting it in the URL. You could
retrieve easily you're tracking info from a HttpSession object just like
from a HashTable instead of parsing thru you're whole URL to get the
info. HTH.
Winston
India
>----------
>From: Moiz Mehmood Hussain[SMTP:[EMAIL PROTECTED]]
>Reply To: A mailing list for discussion about Sun Microsystem's Java Servlet
>API Technology.
>Sent: Thursday, May 27, 1999 6:49 AM
>To: [EMAIL PROTECTED]
>Subject: Tracking Route
>
>Hi
>I am currently designing a system in which i have to track the whole route
>taken by the user, i-e the order in which the user has selected the
>different pages, one way that i have thought of is to pass the different
>options that the user has selected in the URL, my code has become a mess,
>any ideas about a cleaner approach ?
>
>Moiz
>Pakistan
>
>
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>
>___________________________________________________________________________
>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
>
___________________________________________________________________________
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
