[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Extending the problems we have with caps to endpoints
From: |
Jonathan S. Shapiro |
Subject: |
Re: Extending the problems we have with caps to endpoints |
Date: |
Tue, 11 Oct 2005 15:01:29 -0400 |
On Tue, 2005-10-11 at 20:19 +0200, Espen Skoglund wrote:
> [ness ]
> >> For a while, I had them convinced that they wanted it. Then they
> >> looked at the required interaction with the rest of the mapping
> >> database and decided that it would be very difficult to add to
> >> their existing system.
>
> > I don't really understand that. In my understanding copying sth. to
> > s.o. means mapping it from the parent. So if you have
>
> On paper it is really easy, yes. It all boils down to how easy it is
> to find your parent. Depending on your particular implementation of
> the mapping databse this might be a really expensive and complex
> operation.
Hmm. It occurs to me that this may not be the whole problem. Consider
the case of a capability that is NEVER transferred with a MAP operation.
In this case there *is* no parent.
Is it possible that this introduced a problem? If so, I think there may
be a straightforward solution.
shap
Re: Extending the problems we have with caps to endpoints, ness, 2005/10/11