On Wed, 22 Oct 2003, Chris Muller wrote:

> Nothing more than serialize the requests, first come, first serve.  Two
> adds of the same object results in having two pointers to it from the mc
> (think Bag).  Requests for removal of absentees are inhaled silently.

But how is this implemented?  I guess MagmaCollections special-cased by
the transaction system?
If I wanted to implement my own conflict-reduced class, what would I have
to do?