CapTP
From Erights
(Difference between revisions)
Kevin Reid (Talk | contribs) (improve links) |
Kevin Reid (Talk | contribs) (link to erights.org document) |
||
Line 1: | Line 1: | ||
+ | See [http://www.erights.org/elib/distrib/captp/] for description and protocol documentation. | ||
+ | |||
== Data-E configuration == | == Data-E configuration == | ||
Revision as of 18:51, 8 August 2007
See [1] for description and protocol documentation.
Data-E configuration
CapTP as fully implemented in E-on-Java uses Java serialization. The work-in-progress implementation of CapTP in E uses Data-E to serialize CapTP message arguments:
(This has all been made up by User:Kevin Reid; please critique.)
The graph exits which are CapTP-specific are:
-
"CapTP_1_descs"
- The uncall recipient for all descriptors. For example, an ImportDesc is represented in Data-E as
CapTP_1_descs.import(importPos)
. -
"CapTP_1_locatorUnum"
- The local presence of the LocatorUnum.
XXX Specify exactly what other graph exits should be available. for now it's the subgraph kit's default scope plus Ref and import__uriGetter.