[Persistence-sig] A simple Observation API

[Shane Hathaway]

On Wed, 31 Jul 2002, Phillip J. Eby wrote:

> In my use case, the transaction will live as an attribute of a root
> "application" object, and application objects will be pooled for use by
> different threads.  Application objects also contain as attributes all
> their connections, data managers, etc.  So everything's pooled together,
> and there's no question of which transaction goes with what.
>
> This approach is virtually identical to what Zope does now, except that
> Zope keeps the transaction with the thread, instead of with the resource pool.

That's an interesting idea.  It should work well (though you'll have a
bootstrapping issue ;-) ).  It may not be necessary, though, for all
transaction coordinators to provide a method for registering a permanent
participant.  It could be a method of a different interface.  Not all
coordinators (i.e. non-pooled) will be able to fulfill the contract as
expected.

Shane