URI Schema » History » Version 3
Version 2 (J. Wienke, 02/21/2011 02:38 PM) → Version 3/59 (J. Wienke, 02/21/2011 03:28 PM)
h1. URI Schema
<pre>
rsb://composite1,composite2.composite3.componentName/interface/port rsb://subscribername.application/path/to/data
rsb://application.publishername/path/to/data
</pre>
h2. Use Cases
* Introspection URIs? HTTP possible?
* Subscription on each node of the tree (aggregation vs. filtering)
* Model vs. System URI? Should not exist?
* Every active object must be identifiable
* Data part of URI? Probably not?
* RESTful API?
<pre>
rsb://composite1,composite2.composite3.componentName/interface/port rsb://subscribername.application/path/to/data
rsb://application.publishername/path/to/data
</pre>
h2. Use Cases
* Introspection URIs? HTTP possible?
* Subscription on each node of the tree (aggregation vs. filtering)
* Model vs. System URI? Should not exist?
* Every active object must be identifiable
* Data part of URI? Probably not?
* RESTful API?