Persisting IdentityDictionary

[Elliot Finley]

On Wed, Apr 27, 2011 at 5:02 PM, Chris Muller <asqueaker at gmail.com> wrote:
> With Magma's networking layer ("Ma client server", which is used
> independently in other apps, without Magma, BTW), it is very easy to
> define new types of requests and responses; they're all first-class
> objects.  So I'm thinking of a new request-type that would be an
> oid-reservation for any uncommitted object so that, if that object is
> ever committed, that's the oid it will get.
>
> The only downside to this is that the whole purpose of
> MagmaPreallocatedDictionary is to be very fast, so we don't want to
> require an extra trip to the server for each and every at:put:.  So
> requests for oid reservations should bring back 100 at a time, and
> sessions can then dole them out one by one as they're requested.  We
> have plenty of oid space, there is no concern about wasting a few oids
> if not all of them get used.

If I were to see a visual diagram of how all the parts of Magma fit
together, I could come up to speed faster.  Coding this is a little
beyond me at the moment.

Elliot