- From: Aaron Boodman <aa@google.com>
- Date: Wed, 17 Oct 2007 02:29:33 -0700
On 10/17/07, Maciej Stachowiak <mjs at apple.com> wrote: > - An author mistake (like doing something that causes an exception in > the callback) means a stuck lock, quite possibly ruining the whole > session. I can say from experience that this is a very real problem. It is probably the number one problem that people run into with the current Gears API. Another problem is that developers actually don't realize they need to use BEGIN and COMMIT and they end up writing extremely slow code and wondering why. Making the transactions be automatic is a big win for making the API performant by default. I think it's worthwhile to iron out the problems with the implicit transaction and changeVersion, instead of just using a simple api. - a
Received on Wednesday, 17 October 2007 02:29:33 UTC