Re: Backtracking woes
Re: Backtracking woes
- Subject: Re: Backtracking woes
- From: MacFirst <email@hidden>
- Date: Wed, 15 Sep 2004 19:46:14 -0700
on 9/15/04 1:33 PM, Benjamin Adair <email@hidden> went on and on
saying, in part:
> 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.
EditingContexts. By and large, EC-s aren't very browser-back-button
friendly. So you need to devise a way to make sure that the edits on a
particular page happen in their own EC, and are saved as appropriate.
In general, I use the session.ec for displaying but, if there's data to be
edited, I re-fetch it into its own EC (which I cache with the page), and be
sure to grab local copies of anything that might be made part of a
relationship.
That's pretty rough but, if you think about changes taking place in an EC,
and how the browser back button works, you can probably see where your
problem is.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden