• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Undo manager and AJAX
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Undo manager and AJAX


  • Subject: Re: Undo manager and AJAX
  • From: Daniel Beatty <email@hidden>
  • Date: Mon, 30 Mar 2009 15:04:42 -0500

Greetings Fredik,
It is not entirely impossible. There are few papers on this subject under the heading Delta-Grid by Susan Urban. The general idea is that the "undo" manager has take in consideration all applications (processes) that write to it. On writing, a change record derived from the database's log stream is used to establish a set transaction list that constitutes the undo stack.


The trouble for most WO apps is that such an undo inherently means changing state for other connected clients that have data check out from clean to dirty, which they will only discover on submission.

I hope that helps a little bit.

Later,
Dan Beatty
Ph.D. Student
Texas Tech University



On Mar 30, 2009, at 10:03 AM, Fredrik Lindgren wrote:

OK! Seems like I should keep away then!

Regards
/Fredrik

30 mar 2009 kl. 16.54 skrev Anjo Krank:




Am 30.03.2009 um 16:27 schrieb Mike Schrag:

That said, I'm not sure undo conceptually really works out in EOF, anyway
You sure about that? Or is it just unreliable?
It _works_ -- that was maybe a bit too bold .. However, when you stop using session.default, and start using lots of peers that are very transient, I believe that ends up not really working out practically. Doesn't each EC have its own undo manager on it, so you would only be able to undo the transactions from a single EC and it wouldn't be aware of its peers' transactions?

From what I understood, this was mainly for undoing changes from an ECs POV, so deletes would get re-inserted etc. As far as this makes sense... e.g. your didInsert() code would get called again wreaking whatever havoc you'd expect after such a move.


Cheers, Anjo

_______________________________________________
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


_______________________________________________ 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

_______________________________________________ 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
References: 
 >Undo manager and AJAX (From: Fredrik Lindgren <email@hidden>)
 >Re: Undo manager and AJAX (From: Mike Schrag <email@hidden>)
 >Re: Undo manager and AJAX (From: Anjo Krank <email@hidden>)
 >Re: Undo manager and AJAX (From: Mike Schrag <email@hidden>)
 >Re: Undo manager and AJAX (From: Anjo Krank <email@hidden>)
 >Re: Undo manager and AJAX (From: Fredrik Lindgren <email@hidden>)

  • Prev by Date: Re: JavaClient session timeout?
  • Next by Date: Re: modeling problem
  • Previous by thread: Re: Undo manager and AJAX
  • Next by thread: modeling problem
  • Index(es):
    • Date
    • Thread