CapTP - Revision history

Kevin Reid: +cat Pluribus

2009-06-10T16:04:29Z

+cat Pluribus

New page

See [http://www.erights.org/elib/distrib/captp/] for description and protocol documentation. The material should be moved here and rewritten into a specification.

Links to specification details should go right here.

== Specification exits ==

The CapTP specification, per se, does not specify these choices:

# The [[Miranda protocol]] all objects exposed over CapTP are expected to respond to. CapTP requires at least [[Miranda whenMoreResolved|__whenMoreResolved]].
# The format in which CapTP messages are serialized for transmission over a byte stream.
## The format in which objects embedded in CapTP messages are serialized in that stream.
### The set of [[graph exit]]s; that is, those objects/[[maker]]s which both ends know about and can refer to in their serialized objects. The [[ad-hoc serialization comity]] proposal would mitigate this.

In an [[E]] system, these holes are specified to be filled with, respectively:

# [[Miranda protocol]]
# {{XXX|Write this specification. See CapTP impl in E-on-CL}}
## Data-E, with CapTP-specific details as [[#Data-E configuration|below]].

== 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 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_locatorUnum"</code> : 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]]}}.

[[Category:To be specified]]
[[Category:E specification]]
[[Category:Pluribus]]

Kevin Reid: fix Miranda protocol link

2009-05-19T23:07:06Z

fix Miranda protocol link

←Older revision		Revision as of 23:07, 19 May 2009
Line 7:		Line 7:
	The CapTP specification, per se, does not specify these choices:		The CapTP specification, per se, does not specify these choices:

-	# The ~~set of~~ [[Miranda ~~messages~~]] all objects exposed over CapTP are expected to respond to. CapTP requires at least [[Miranda whenMoreResolved\|__whenMoreResolved]].	+	# The [[Miranda protocol]] all objects exposed over CapTP are expected to respond to. CapTP requires at least [[Miranda whenMoreResolved\|__whenMoreResolved]].
	# The format in which CapTP messages are serialized for transmission over a byte stream.		# The format in which CapTP messages are serialized for transmission over a byte stream.
	## The format in which objects embedded in CapTP messages are serialized in that stream.		## The format in which objects embedded in CapTP messages are serialized in that stream.

Kevin Reid: /* Data-E configuration */ use xxx template

2009-05-16T04:35:57Z

Data-E configuration: use xxx template

←Older revision		Revision as of 04:35, 16 May 2009
Line 29:		Line 29:
	; <code>"CapTP_1_locatorUnum"</code> : The local presence of the [[LocatorUnum]].		; <code>"CapTP_1_locatorUnum"</code> : 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]].	+	{{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]]}}.

	[[Category:To be specified]]		[[Category:To be specified]]
	[[Category:E specification]]		[[Category:E specification]]

Kevin Reid: talk about spec holes

2009-04-30T19:24:14Z

talk about spec holes

←Older revision		Revision as of 19:24, 30 April 2009
Line 1:		Line 1:
-	See [http://www.erights.org/elib/distrib/captp/] for description and protocol documentation.	+	See [http://www.erights.org/elib/distrib/captp/] for description and protocol documentation. The material should be moved here and rewritten into a specification.
		+
		+	Links to specification details should go right here.
		+
		+	== Specification exits ==
		+
		+	The CapTP specification, per se, does not specify these choices:
		+
		+	# The set of [[Miranda messages]] all objects exposed over CapTP are expected to respond to. CapTP requires at least [[Miranda whenMoreResolved\|__whenMoreResolved]].
		+	# The format in which CapTP messages are serialized for transmission over a byte stream.
		+	## The format in which objects embedded in CapTP messages are serialized in that stream.
		+	### The set of [[graph exit]]s; that is, those objects/[[maker]]s which both ends know about and can refer to in their serialized objects. The [[ad-hoc serialization comity]] proposal would mitigate this.
		+
		+	In an [[E]] system, these holes are specified to be filled with, respectively:
		+
		+	# [[Miranda protocol]]
		+	# {{XXX\|Write this specification. See CapTP impl in E-on-CL}}
		+	## Data-E, with CapTP-specific details as [[#Data-E configuration\|below]].

	== Data-E configuration ==		== Data-E configuration ==
Line 15:		Line 32:

	[[Category:To be specified]]		[[Category:To be specified]]
		+	[[Category:E specification]]

Kevin Reid: Reverted edits by Zarutian (Talk); changed back to last version by Kevin Reid

2008-09-18T11:00:09Z

Reverted edits by Zarutian (Talk); changed back to last version by Kevin Reid

←Older revision		Revision as of 11:00, 18 September 2008
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 [[~~Data-E#~~graph exit\|graph exits]] which are CapTP-specific are:	+	The [[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>.

Zarutian: I have no idea how you link to an article subsection. So please fix it

2008-09-17T02:20:45Z

I have no idea how you link to an article subsection. So please fix it

←Older revision		Revision as of 02:20, 17 September 2008
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>.

Kevin Reid: link to erights.org document

2007-08-08T18:51:59Z

link to erights.org document

←Older revision		Revision as of 18:51, 8 August 2007
Line 1:		Line 1:
		+	See [http://www.erights.org/elib/distrib/captp/] for description and protocol documentation.
		+
	== Data-E configuration ==		== Data-E configuration ==

Kevin Reid: improve links

2007-08-08T18:45:27Z

improve links

←Older revision		Revision as of 18:45, 8 August 2007
Line 1:		Line 1:
	== Data-E configuration ==		== 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:	+	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 [[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 [[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/~~index.html~~#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>.
	; <code>"CapTP_1_locatorUnum"</code> : The local presence of the [[LocatorUnum]].		; <code>"CapTP_1_locatorUnum"</code> : The local presence of the [[LocatorUnum]].

Kevin Reid: add experimental specification of Data-E exits

2007-08-08T18:44:05Z

add experimental specification of Data-E exits

←Older revision		Revision as of 18:44, 8 August 2007
Line 1:		Line 1:
-	~~See [http://www.erights.org/elib/distrib/captp/] for description and protocol documentation. The material should be moved here and rewritten into a specification.~~
-
-	~~Links to specification details should go right here.~~
-
-	~~== Specification exits ==~~
-
-	~~The CapTP specification, per se, does not specify these choices:~~
-
-	~~# The [[Miranda protocol]] all objects exposed over CapTP are expected to respond to. CapTP requires at least [[Miranda whenMoreResolved\|__whenMoreResolved]].~~
-	~~# The format in which CapTP messages are serialized for transmission over a byte stream.~~
-	~~## The format in which objects embedded in CapTP messages are serialized in that stream.~~
-	### The set of [[graph exit]]s; that is, those objects/[[maker]]s which both ends know about and can refer to in their serialized objects. The [[ad-hoc serialization comity]] proposal would mitigate this.
-
-	~~In an [[E]] system, these holes are specified to be filled with, respectively:~~
-
-	~~# [[Miranda protocol]]~~
-	~~# {{XXX\|Write this specification. See CapTP impl in E-on-CL}}~~
-	~~## Data-E, with CapTP-specific details as [[#Data-E configuration\|below]].~~
-
	== Data-E configuration ==		== 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:	+	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.)	+	(This has all been made up by [[Kevin Reid]]; please critique.)

	The [[graph exit\|graph exits]] which are CapTP-specific are:		The [[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/index.html#descriptors descriptors]. For example, an [[ImportDesc]] is represented in Data-E as <code>CapTP_1_descs.import(importPos)</code>.
	; <code>"CapTP_1_locatorUnum"</code> : The local presence of the [[LocatorUnum]].		; <code>"CapTP_1_locatorUnum"</code> : 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]]}}.	+	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]].

	[[Category:To be specified]]		[[Category:To be specified]]
-	~~[[Category:E specification]]~~
-	~~[[Category:Pluribus]]~~