[Persistence-sig] Clearing participants (was Observation API)

[Jeremy Hylton]

>>>>> "PJE" == Phillip J Eby <pje@telecommunity.com> writes:

  PJE> My motivation for making registration permanent in my "Straw
  PJE> Man" transaction API proposal was to counteract this.  In the
  PJE> API Shane and I are discussing, there would be an option to
  PJE> register with a transaction instance such that the registration
  PJE> would remain across commit/rollback boundaries.

I don't think it makes sense to talk about a single transaction that
spans multiple commits.  A transaction ends with a commit or an abort.
If you do something after that, it's a different transaction.

I agree, however, that it is worth discussing 1) what mechanisms are
needed for associating threads with transactions in order to support a
range of policies and 2) how a resource manager can express its
interest in all (some?) transactions.  The second issue probably
depends on the first, but not vice versa.

Jeremy