One thing to note about history.go(-1); it that it will take you back a page in your browser's cache with no trip to server. Creating a link using either the session or referrer will re-send the page request to the server, and will get you a "fresh" copy of the page (meaning that if the data has changed on the previous page, you'll get the latest version. Using the browsers cache is obviously faster to the user, but they might see a "stale" page.
Which way is preferred? Well, it's hard to say. You could argue that if the link said "back", and the user clicked it and saw a different version of the page, they might be confused (for instance, returning back to a search results page where the user wanted to click through a different search result link they had just seen, but when they clicked "back", the search results changed and the link they wanted is now gone). On the other hand, if you're developing a web application with many users interacting with the same data, you probably would always want your user to see the latest data from the database, in which case, you'd avoid using the "history.go(-1)" method, and possibly disabling the browser's back button with javascript. NOSLOW --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
