[e-cvs] cvs commit: e/doc/elib/distrib/captp WormholeOp.html
markm@eros.cs.jhu.edu
markm@eros.cs.jhu.edu
Sat, 12 May 2001 22:48:28 -0400
markm 01/05/12 22:48:28
Modified: doc/elib/distrib/captp WormholeOp.html
Log:
typo
Revision Changes Path
1.3 +8 -8 e/doc/elib/distrib/captp/WormholeOp.html
Index: WormholeOp.html
===================================================================
RCS file: /cvs/e/doc/elib/distrib/captp/WormholeOp.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- WormholeOp.html 2001/05/09 20:46:29 1.2
+++ WormholeOp.html 2001/05/13 02:48:28 1.3
@@ -123,14 +123,14 @@
say Carol in VatC. If T is passed to Alice in VatA, everything's cool,
and it arrives with a Far reference to Carol as its key. However,
if Alice were to further pass this to Bob in VatB, then, in order
- for T to still be operational and the moment of arrival, this key
- would have to arrive as a Settled remote reference to Carol, which
- is to say, a Far reference. (For reasons explained below, E won't
- do this until the WormholeOp is implemented. Instead, in current E
- implementations, the reference to Carol will arrive as an Unresolved
- remote reference (a RemoteVow), and therefore T will fail to unserialize.
- This is the <a href="../../equality/same-ref.html#lost-resolution">Lost
- Resolution</a> bug.)</p>
+ for T to still be operational at the moment of arrival, this key would
+ have to arrive as a Settled remote reference to Carol, which is to
+ say, a Far reference. (For reasons explained below, E won't do this
+ until the WormholeOp is implemented. Instead, in current E implementations,
+ the reference to Carol will arrive as an Unresolved remote reference
+ (a RemoteVow), and therefore T will fail to unserialize. This is the
+ <a href="../../equality/same-ref.html#lost-resolution">Lost Resolution</a>
+ bug.)</p>
</li>
</ul>
<p>The conflict arises when, in the Preserve Passability scenario, Alice