> Even with transactions, you are going to need to handle those
transactions
> appropriately. In other words, what do you do on failure? You rollback,
but
> then what?
Point taken, but I'd rather report a lame error to the client than mess
up the integrity of the database. I'm thinking of those textbook examples
where client B writes an improper balance back into the bank database
because it hasn't seen client A's withdrawal yet.
> In Scarab's view, so far, we just do things on a first come first served
> basis. If two people are working on the same issue, right now, there is a
> chance that things could become out of sync ui wise. Eventually, we will
> build a system on top of that that will present a UI that allows people
to
> handle that case more gracefully.
Whoa. And I thought you were a java zen master... ;-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
