I have seen this approach, but I frankly don't see how it is any easier, as well as it adds more objects than what I proposed. I say this mostly because when you get to page C you almost always got there by way of page b. The "stack" on page C would be a, b and c (c refreshing itself basically, or not being a link at all, but just text to show where you are at). I am not quite sure I understand why you need to "push" the page onto a stack and keep track of it in that manner. I know it can be done this way, I just think its overkill. But I am definitely all years on an explanation as to why this is a good solution. The only reason I can think of this is for a "back button" history, where instead of on page c you know page a and b were before it, you keep track of the course of actions they took to get to it. For example, where I can see this being beneficial is if on page c, you click A to go to page a. Now, on page a, instead of showing just a, you would see c | a because the user came from page c. So, they can click on c to go BACK to that page. The only other reason I can see the use of this "history" in such a fashion is to keep accurate data the user entered at each step of the way. For example, they are on page c, enter some data, then go back to page a and modify something, then jump back to c. Page c now shows what they typed, but if they modify something on c, then hit the C, it would return them to the page c BEFORE they modified any fields on that page. In order to facilitate this you would want to create a sort of Page object, like a HashMap of each page and all of its elements (including data for them) so as to keep an accurate "history" list..infact I would call this an Undo list because it would allow you to back up to previous modifications, sort of restoring the state of each page in the way it was when you left it. But please, fill me (and others I presume) in on why the use of a stack is used? I do think it really depends on the complexity you need. As I said previously, if all you want is the ability to jump to any page prior to the page your on, then jump back, so long as you don't need dynamic creation of pages based on previous page input, you should be fine with a static set of links on each page.
> -----Original Message----- > From: Mariappan Vaithianathan (CTC) > [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 31, 2001 12:30 PM > To: [EMAIL PROTECTED] > Subject: Re: capturing a user's navigation history > > > best way is to maintain stack....create a stack object and > keep placing the > files in that like > o_Stack.push(sessObj.getValue("TerminatingJSP")); and then > retrieve them > accordingly! it will be LIFO as u might have guessed! > > > Rgds > Mariappan > Ph.: 6256437 Extn.: 321 > > > > -----Original Message----- > > From: Schulz Ryan C [SMTP:[EMAIL PROTECTED]] > > Sent: Thursday, November 01, 2001 1:44 AM > > To: [EMAIL PROTECTED] > > Subject: capturing a user's navigation history > > > > Has anyone tried capturing a user's history, capturing > where they've been > > as > > they work their way through an application. In turn, I > would like to > > create > > a "breadcrumb" trail of navigation, giving them the ability > to go back to > > any part of their work in the application for a particular session. > > > > Example: > > Home :: Search Results :: Details :: More Info > > > > Thanks! > > > > > ============================================================== > ============ > > = > > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff > > JSP-INTEREST". > > For digest: mailto [EMAIL PROTECTED] with body: "set > JSP-INTEREST > > DIGEST". > > Some relevant FAQs on JSP/Servlets can be found at: > > > > http://archives.java.sun.com/jsp-interest.html > > http://java.sun.com/products/jsp/faq.html > > http://www.esperanto.org.nz/jsp/jspfaq.jsp > > http://www.jguru.com/faq/index.jsp > > http://www.jspinsider.com > > ============================================================== > ============= > To unsubscribe: mailto [EMAIL PROTECTED] with body: > "signoff JSP-INTEREST". > For digest: mailto [EMAIL PROTECTED] with body: "set > JSP-INTEREST DIGEST". > Some relevant FAQs on JSP/Servlets can be found at: > > http://archives.java.sun.com/jsp-interest.html > http://java.sun.com/products/jsp/faq.html > http://www.esperanto.org.nz/jsp/jspfaq.jsp > http://www.jguru.com/faq/index.jsp > http://www.jspinsider.com > =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
