l4-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cancellation forwarding protocol (was Re: Reliability of RPC service


From: Bas Wijnen
Subject: Re: Cancellation forwarding protocol (was Re: Reliability of RPC services)
Date: Fri, 28 Apr 2006 14:06:52 +0200
User-agent: Mutt/1.5.11+cvs20060403

On Thu, Apr 27, 2006 at 04:06:35PM -0400, Jonathan S. Shapiro wrote:
> Because of this, the operation that you want here is Discrim.
> 
> HOWEVER!!!
> 
> This case is so universal that there will be a safeGetType() method on
> the discrim interface. Discrim.safeGetType() will perform:
> 
>    {
>       if (discrim.classify(theCap) == ctInvalid
>            return ctInvalid;
>         else
>            return theCap.getType();
>    }
> 
> This is actually implemented at the library level, and I had forgotten
> about it.

So if the capability is invalid, it isn't invoked, but ctInvalid is returned
instead.  However, if it is valid, the capability is invoked in order to get
the type, and a reply capability is thereby invalidated.

How does this differ from simply calling theCap.getType()?

Thanks,
Bas

-- 
I encourage people to send encrypted e-mail (see http://www.gnupg.org).
If you have problems reading my e-mail, use a better reader.
Please send the central message of e-mails as plain text
   in the message body, not as HTML and definitely not as MS Word.
Please do not use the MS Word format for attachments either.
For more information, see http://129.125.47.90/e-mail.html

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]