Yes..we have. It can be easy or hard, depending on some situations. For example:
a | b | c | d If they are on page d, then click on b, potentially they can modify something on page b that may alter how page c (and then d) are displayed. Therefore, while it isn't difficult to allow them to go back, it may be harder to return to a given page based on what they may have modified. You can programatically check for these differences, but the more complex your requirements are (for example, page c depends specifically on one (or more) fields of page b to be properly rendered, and thus page d is based on choices of page c), the harder it will be to provide a fully circular history where they can jump back and forth. On the other hand, if each successive page is not dependent on the previous, then it is quite a bit easier. You simply keep track of what the "latest" page they were at, and using some sort of "include" or something (so that you don't have to code it on every page, just include the one file that has the display logic for the pages they have been to and can select) on each page, your all set. There is ofcourse other meanings behind your question. Is it a click stream your after, to keep tabs on EVERY page they visit, stored in a database so that your CR department can pull it up should a problem arise? That isn't hard to implement either, but every page will require a database transaction to store the click stream entries as the user navigates. This table can get quite large so be prepared, depending on the number of users on your site, to fine tune this table, and/or remove entries after x number of days to keep its size down. Writing an agent that runs every 24 hours or so and queries any activity older than x days from the run time date is an easy way to avoid having to manually remove entries after so many days. > -----Original Message----- > From: Schulz Ryan C [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 31, 2001 12:14 PM > 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
