@Bob, I forgot to ask when I replied ... how effective did you find that solution? any gotcha's or points to consider?
>> Do the records in the tables contain >> a column that is updated on every transaction? Like a >> LastUpdateTimestamp, or unique id? And if they do, is that info >> available to you via the webservice interface? > > I think I can see what you're getting at: use the timestamp to check > for data concurrency of the records being edited and tie that in to a > memento pattern. > > I thing that's going to beat me is how to handle a network outage part > of the way thru the writing process - where some entities get updated > but others are left hanging/untouched (when they should be changed to > match the others). The memento pattern may be able to hold onto the > "state" of all the entities, but there's no way to reach out to them > to roll them back if the network is down. In the case of a network > outage, I'd really need the whole lot to fail so it can be re-run, > rather than being half pregnant... > > outage includes brown-outs and high traffic causing time-outs. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
