Re: Best Practice on Uncommitted Changes in EC
Re: Best Practice on Uncommitted Changes in EC
- Subject: Re: Best Practice on Uncommitted Changes in EC
- From: Sacha Mallais <email@hidden>
- Date: Fri, 8 Apr 2005 14:03:33 -0700
On Apr 8, 2005, at 1:27 pm, James Cicenia wrote:
Well - I saw this issue early on as being a problem so we made the
command decision to use a popup for the majority of our edits and
inserts. This way you can just create a new ec for that popup and not
care if they close it, or save or cancel it. This practice has worked
well for us.
Do you also spawn a new session? You solution works well, but still
has a problem if you use the edit page a bunch of times in a row --
enough to push the other pages out of the cache -- in which case your
users will not be able to go back to the main app page...
sacha
--
Sacha Michel Mallais - 400 lb. chimp
Global Village Consulting Inc.: http://www.global-village.net/
The bird of paradise alights only upon the hand that does not grasp.
_______________________________________________
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