Re: Browser behavior in remembering parameters

Replies are listed 'Best First'.
Re^2: Browser behavior in remembering parameters by seefurst (Initiate) on May 08, 2012 at 15:52 UTC
That's what cookies are for? Why not just store all choices in a cookie and then update the cookie as necessary. That way no matter where they are, their choices are there, their pathways are preserved. You can detect if a browser doesn't take cookies. Also, the links should still be the same if they click back, because, in most cases the page is rendered from a local cache and not from the server.	[reply]
Re^3: Browser behavior in remembering parameters by Anonymous Monk on May 08, 2012 at 16:06 UTC
That's what cookies are for? .... If you're referring to the rest of the question, cookies should only be used to brand a browser, the beginnings of session managment. It is basic boring already invented stuff you shouldn't reinvent :) Read all about it, watch the videos and slideshows Web Programming: For Beginners, Recommendations for client-side state management, web applications: what is the correct way to realise web applications, Mod_Survey or dive right in cgi-app / mojo / dancer / catalyst to start writing perl web apps	[reply]
Re^4: Browser behavior in remembering parameters by perlrookie1 (Initiate) on May 10, 2012 at 11:25 UTC
Thanks a lot for your replies. OK now, here lies the problem. I cant use sessions because I am forbidden to do so due to some reasons. And neither am I too keen on using cookies since there is a chance that some paranoid users may have disabled cookies in their browsers. So that lead me to think that since this involves the click on just one browser back button, would it be safe to go ahead with such an arrangement?	[reply]
Re^5: Browser behavior in remembering parameters by aaron_baugher (Curate) on May 10, 2012 at 23:03 UTC
Re^5: Browser behavior in remembering parameters by Anonymous Monk on May 10, 2012 at 21:09 UTC