https://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732015-01-27T12:07:26ZOpen Source Collaboration PlatformRobotics Service Bus - Bug #2163: Remove rsb.wire-schema property from metaData in socket transporthttps://code.cor-lab.de/issues/2163?journal_id=65302015-01-27T12:07:26ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<ul><li><strong>Description</strong> updated (<a href="/journals/diff/6530?detail_id=7629" title="View differences">diff</a>)</li></ul> Robotics Service Bus - Bug #2163: Remove rsb.wire-schema property from metaData in socket transporthttps://code.cor-lab.de/issues/2163?journal_id=65312015-01-27T12:08:51ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<ul></ul><p>This is basically an implementation detail and not intended for client usage. Such information should normally only be used inside converters, since there are transports like inprocess where no wire schema exists at all.</p> Robotics Service Bus - Bug #2163: Remove rsb.wire-schema property from metaData in socket transporthttps://code.cor-lab.de/issues/2163?journal_id=65322015-01-27T14:24:35ZR. Haschkerhaschke@techfak.uni-bielefeld.de
<ul></ul><p>From my point of view, the socket transport should use the internal Notification data structures to access the wire-schema, instead of cluttering the metaData. What if, the user wants to set a property rsb.wire-schema herself? ;-)</p> Robotics Service Bus - Bug #2163: Remove rsb.wire-schema property from metaData in socket transporthttps://code.cor-lab.de/issues/2163?journal_id=65332015-01-27T15:45:52ZR. Haschkerhaschke@techfak.uni-bielefeld.de
<ul><li><strong>Subject</strong> changed from <i>non-uniform event format in socket/spread transport</i> to <i>remove rsb.wire-schema property from metaData in socket transport</i></li><li><strong>Target version</strong> set to <i>rsb-0.12</i></li></ul><p>The only way to robustly access the wireschema is at conversion time. <br />There is the rsb::converter::SchemaAndByteArrayConverter for this purpose.</p>
<p>Nevertheless, the socket transport should remove the rsb.wire-schema property from metaData.</p> Robotics Service Bus - Bug #2163: Remove rsb.wire-schema property from metaData in socket transporthttps://code.cor-lab.de/issues/2163?journal_id=65342015-01-29T09:24:33ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Category</strong> changed from <i>C++</i> to <i>Specification</i></li></ul><p>R. Haschke wrote:</p>
<blockquote>
<p>The only way to robustly access the wireschema is at conversion time. <br />There is the rsb::converter::SchemaAndByteArrayConverter for this purpose.</p>
</blockquote>
<p>For arbitrary user code, yes. However, tools such as the loggers may want to receive deserialized payloads along with "best effort" transport-specific meta-data such as wire-schema, notification size or serialized payload size. This is an "best effort" protocol because some transports conceptually cannot provide this information and other transport implementations may not have the necessary code.</p>
<blockquote>
<p>What if, the user wants to set a property rsb.wire-schema herself? ;-)</p>
</blockquote>
<p>I think this information is currently missing in the specification, but the idea of meta-data items named <code>rsb.*</code> was that they are reserved for RSB and thus user code should not attempt to create such meta-data items. In general, user code should not make assumptions about the presence or absence of any meta-data item.</p>
<blockquote>
<p>Nevertheless, the socket transport should remove the rsb.wire-schema property from metaData.</p>
</blockquote>
I see a number of possibilities here:
<ol>
<li>Do not create the meta-data item, as suggested above</li>
<li>Adapt the Spread transport to also create the meta-data item (if it does not already)</li>
<li>Make the creation of such meta-data item configurable via an option of the respective transport (the CL implementation does this for a number of similar meta-data items). Tools such as loggers can then explicitly request the meta-data items.</li>
</ol> Robotics Service Bus - Bug #2163: Remove rsb.wire-schema property from metaData in socket transporthttps://code.cor-lab.de/issues/2163?journal_id=68312015-04-27T09:05:27ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<ul><li><strong>Target version</strong> changed from <i>rsb-0.12</i> to <i>rsb-0.13</i></li></ul> Robotics Service Bus - Bug #2163: Remove rsb.wire-schema property from metaData in socket transporthttps://code.cor-lab.de/issues/2163?journal_id=79252016-03-02T07:55:49ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Target version</strong> changed from <i>rsb-0.13</i> to <i>rsb-0.14</i></li></ul> Robotics Service Bus - Bug #2163: Remove rsb.wire-schema property from metaData in socket transporthttps://code.cor-lab.de/issues/2163?journal_id=82482016-05-13T11:58:58ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Target version</strong> changed from <i>rsb-0.14</i> to <i>rsb-0.15</i></li></ul> Robotics Service Bus - Bug #2163: Remove rsb.wire-schema property from metaData in socket transporthttps://code.cor-lab.de/issues/2163?journal_id=87302016-09-28T12:29:23ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Target version</strong> changed from <i>rsb-0.15</i> to <i>rsb-0.16</i></li></ul> Robotics Service Bus - Bug #2163: Remove rsb.wire-schema property from metaData in socket transporthttps://code.cor-lab.de/issues/2163?journal_id=91722017-04-10T18:59:12ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Target version</strong> changed from <i>rsb-0.16</i> to <i>rsb-0.17</i></li></ul> Robotics Service Bus - Bug #2163: Remove rsb.wire-schema property from metaData in socket transporthttps://code.cor-lab.de/issues/2163?journal_id=93052017-10-10T16:18:54ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<ul><li><strong>Subject</strong> changed from <i>remove rsb.wire-schema property from metaData in socket transport</i> to <i>Remove rsb.wire-schema property from metaData in socket transport</i></li><li><strong>Target version</strong> changed from <i>rsb-0.17</i> to <i>rsb-0.18</i></li></ul>