CapTP

From Erights

(Difference between revisions)
Jump to: navigation, search
(link to erights.org document)
(I have no idea how you link to an article subsection. So please fix it)
Line 7: Line 7:
(This has all been made up by [[User:Kevin Reid]]; please critique.)
(This has all been made up by [[User:Kevin Reid]]; please critique.)
-
The [[graph exit|graph exits]] which are CapTP-specific are:
+
The [[Data-E#graph exit|graph exits]] which are CapTP-specific are:
; <code>"CapTP_1_descs"</code> : The uncall recipient for all [http://www.erights.org/elib/distrib/captp/#descriptors descriptors]. For example, an [[ImportDesc]] is represented in Data-E as <code>CapTP_1_descs.import(importPos)</code>.
; <code>"CapTP_1_descs"</code> : The uncall recipient for all [http://www.erights.org/elib/distrib/captp/#descriptors descriptors]. For example, an [[ImportDesc]] is represented in Data-E as <code>CapTP_1_descs.import(importPos)</code>.

Revision as of 02:20, 17 September 2008

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.

Personal tools
more tools