Here's a scenario that is giving me conniptions today:
So clearly there is some caching going on here, and the second page takes some liberties with parameter name/value pairs when multiple pages are called in rapid succession -- in this case, it appears to use the previous eventid value (5) rather than the current one (6). Is there a way around this? Can my life be good again?
- User calls an AW5 page like this: www.somepage.html?familyid1=4&eventid2=5
- The page loads, user types some info and submits the page, at which point the database is updated with familyid1=4 and eventid2=5. Life is good.
- User exits the page and loads a different page within one minute or so (the page is different but the parameter names are the same: familyid and eventid). In this example the second call uses a different "eventid" parameter value, such as: www.someOTHERpage.html?familyid1=4&eventid2=6
- The page loads, user types some info and saves the page. However, at this point the database is updated with familyid=4 and eventid=5 (rather than eventid=6.) Life is bad.
- If the user waits a few minutes between the two calls to the different pages that have the same parameter names but different values passed in, the database is updated properly, in this case familyid=4 and eventid=6. Life is good again, sort of. Ditto if the user closes and restarts the browser between the two calls.
So clearly there is some caching going on here, and the second page takes some liberties with parameter name/value pairs when multiple pages are called in rapid succession -- in this case, it appears to use the previous eventid value (5) rather than the current one (6). Is there a way around this? Can my life be good again?
Comment