[Jsdc-info] Should i call it transactions?
Brought to you by:
zig007
From: JSDC u. information. <jsd...@li...> - 2007-02-19 21:04:18
|
I am currently implementing functionality that groups actions into = larger entities.=20 =20 This is for two reasons:=20 =20 * When a user clicks the undo button, the user wants the application to = undo what the user did. Not one of the, say, twenty-four thousand = aggregate calculations that was the consequence of that action.=20 =20 * To mimic the behavior of a real transactional database, where a = procedure can return to a known state if something goes wrong during an = operation involving multiple steps.=20 =20 So. This is beginning to look an awful lot like transactions. Of course = JSDC can't control it's environment like a database can so it will never = be exactly like the real thing. On the other hand, one could say that it = is real transactions since JSDC doesn't have constraints and locks that = can be violated.=20 Also, a javascript application is currently a strictly single user = thing.=20 Hence, i'm leaning towards calling it transactions. =20 =20 Neat, huh? =20 =20 //Zig007=20 =20 PS.=20 To call the JSDC data handling a transactional database system might = still a bit of a stretch :-)=20 DS. =20 Project home:=20 http://sourceforge.net/projects/jsdc/ |