Hello all,
I'm getting bit by the whole backtracking thing. I've created a simple
web application to allow our webmaster to maintain the users and groups for
our web site which authenticates against a MySQL database.
I'm finding pretty much that whenever the user moves forward within the
application logic and then backtracks within the browser and attempts to do
something else, the application's state doesn't match and I'm having a
difficult time thinking of a way (short of setting the backtrack cache to 0 -
which doesn't really help so much when the browser doesn't refresh the page in
the first place and is so user-unfriendly) to work around things.
A specific example. I have a ivar, resultSetCurrentPage. If the user proceeds to the 2nd page, which increments the ivar, backtracks, and then
attempts to edit a user listed on what was the first page.. They'll end up
editing the corresponding user from the second page.
I have read through the following chapter on backtracking:
http://developer.apple.com/documentation/WebObjects/Web_Applications/BacktrackingAndCache/chapter_6_section_1.html#//apple_ref/doc/uid/TP30000111
And have played with settings for 'pageRefreshOnBacktrackEnabled' and
read through messages from the list that I have saved over the past year and
really am not finding much luck.
It is interesting to me that Apple's Webmail application seems to handle
this properly.. You can read a message, back track, select a different message
to read and it loads properly.
Do I need to reorganize my logic? Is there something more I can do? Any
suggestions and help would be greatly appreciated.
TIA
Ben
--
Benjamin Adair
Central Office Database Programmer/Analyst
Cancer & Leukemia Group B
Phone: 773-702-6731
Fax: 312-345-0117
Email: email@hidden
Web: http://www.calgb.org/