[rucksack-devel] transactions and distributed objects

[Nikodemus Siivola]

Marco Baringer <mb at bese.it> writes:

> i really don't think you want user extensible transactions. i believe
> that implementing a transaction object will require enough knowledge
> of rucksack's internals that it will be indistunguishable from a
> change to rucksack itself.
>
> should rucksack offer different isolation levels? that's a completly
> different question (and the answer is probably yes).

To clarify, I didn't mean user-extensible transactions.

I ment that (1) if dispatching on the class of the transactions
is a workable implementation stratefy, then different isolation
levels should be "simple" to achieve, and (2) if we only have
a single isolation level, then I'd perfer it to be to be
fully serializable.

Cheers,

  -- Nikodemus              Schemer: "Buddha is small, clean, and serious."
                   Lispnik: "Buddha is big, has hairy armpits, and laughs."