Re: MVC Architecture and transactions

[Buck <kc2hiz@xxxxxxxxx>]

Joe Pluta wrote:
[regarding commitment control]
> If the program is written correctly, the files will get updated.  If the
> program is not written correctly, commitment control won't help.  The only
> thing commitment control buys you from a file update capability is when an
> I/O error occurs, and frankly, when THAT happens on a System i, you have
> much larger problems.

I have used commitment control in a high transaction rate environment, 
and I have found significant value beyond maintaining RI during a crash. 
 I think that it is important to recognise that there is probably more 
than one update program per file, and they _all_ need to be written 
'correctly,' not just the one under consideration at the moment. 
'Correctly' has many connotations, including the ability of Process 2 to 
not be able to delete an item master record that Process 1 has just 
validated an order against, but not written to disk yet.
  --buck