(Although this is filed under the category "captp",
it's technically a bug in "local elib".)
From
http://www.eros-os.org/pipermail/e-lang/2004-August/010006.html
http://www.erights.org/javadoc/org/erights/e/elib/ref/ProxyResolver.html
I'm experimenting with writing comm systems for E.
The identity of a far reference is based on the
optIdentity argument to
EProxyResolver#run/2, which must be a HONORARY Selfless
object.
Surely this is inappropriate for anything but a single,
relied-upon
comm system? Multiple comm systems (or multiple
instantiations of the
same one) could accidentally (or maliciously) use the
same names for
identifying distinct remote objects (or the same object
accessed via
different code/object-graph/network paths.
Either:
1. allowing Selfish identities (the comm system tracks
them with a
WeakValueMap) or
2. non-HONORARY Selfless objects such as ConstLists
(the comm system
uses a tuple of a private pumpkin and the network
identity of the
remote object)
would be adequate.
A variation of #2 (making the tuple explicit and the
pumpkin
per-connection) would, I think, to remove the need for
EProxyHandler to
correctly respond to sameConnection/1.
