Re: Joins on capabilities that have passed through different membranes

Raoul Duke <[email protected]> Tue, 5 Jan 2016 07:27:57 -0800
Newsgroups gmane.comp.capabilities.general
Message-ID <CAJ7XQb6nqyehCd2GYiZ8z+2W4H7oOvdvUhkYMG0mXE1u1uY-SQ@mail.gmail.com>
--===============5393191442896815503==
Content-Type: multipart/alternative; boundary=089e0160c2b0d45663052897e112

--089e0160c2b0d45663052897e112
Content-Type: text/plain; charset=UTF-8

(I naively think that knowing what the real final endpoint would be in
terms of eg 'eq' is the rare case for OCaps, since in OOP generally ideally
one should have refs to interfaces, and not know/care what is doing the
implementation behind those interfaces, including
proxies/wrappers/delegators.) "This call results in Alice doing Y" is
different than "This call tells Alice to do Y".)

--089e0160c2b0d45663052897e112
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">(I naively think that knowing what the real final endpoint w=
ould be in terms of eg &#39;eq&#39; is the rare case for OCaps, since in OO=
P generally ideally one should have refs to interfaces, and not know/care w=
hat is doing the implementation behind those interfaces, including proxies/=
wrappers/delegators.) &quot;This call results in Alice doing Y&quot; is dif=
ferent than &quot;This call tells Alice to do Y&quot;.)</p>

--089e0160c2b0d45663052897e112--

--===============5393191442896815503==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
cap-talk mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/cap-talk

--===============5393191442896815503==--