Robotics Service Bus: Issueshttps://code.cor-lab.de/https://code.cor-lab.de/favicon.ico?14019720732015-04-02T13:48:19ZOpen Source Collaboration Platform
Redmine Enhancement #2217 (Resolved): bag-cat Should Mention the Loading of Definitions.https://code.cor-lab.de/issues/22172015-04-02T13:48:19ZN. Hafnershinmera@tymoon.eu
<p>The Tutorial page in the Documentation for bag-cat does not mention that for certain .tide files additional definitions need to be loaded through command-line switches. Adding this in would make it a lot more useful, as the error messages printed on missing definitions are everything but helpful to the layman.</p>
<p>Page in question is <a class="external" href="http://docs.cor-lab.de/rsbag-manual/trunk/html/tutorial.html">http://docs.cor-lab.de/rsbag-manual/trunk/html/tutorial.html</a><br />Example command as shown to me by Jan Moringen:<br /><pre><code>bag-cat -I$RST/rst-proto/proto/stable -I$RST/rst-proto/proto/sandbox -l$RST/rst-proto/proto/\*\*/\*.proto data-file.tide</pre></code></p></pre> Enhancement #2201 (Resolved): Add display name to introspectionhttps://code.cor-lab.de/issues/22012015-03-13T11:20:38ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>Add an optional field to the introspection protocol for applications to specify a hand-crafted display name to improve readability. This name should not be set by applications themselves, but should be injectable via RSB options so that system administrators can defined it from the outside, e.g. via vdemo.</p>
<p>The name should be passed into the system via the <code>introspection.displayname</code> config variable.</p>
To implement in:
<ul>
<li><del>protocol</del></li>
<li><del>cpp</del></li>
<li><del>java</del></li>
<li><del>python</del></li>
<li><del>cl</del></li>
<li><del>cl tools</del></li>
<li><del>manual</del></li>
</ul> Enhancement #2198 (Resolved): Spread connection pooling for informers [Python]https://code.cor-lab.de/issues/21982015-03-11T10:46:57ZJ. Wienkejwienke@techfak.uni-bielefeld.deEnhancement #2197 (Resolved): Spread connection pooling for informers [C++]https://code.cor-lab.de/issues/21972015-03-11T10:46:36ZJ. Wienkejwienke@techfak.uni-bielefeld.deEnhancement #2196 (Resolved): Spread connection pooling for informers [Java]https://code.cor-lab.de/issues/21962015-03-11T10:46:07ZJ. Wienkejwienke@techfak.uni-bielefeld.deEnhancement #2151 (Resolved): RSB documentation should include callAsync() exampleshttps://code.cor-lab.de/issues/21512015-01-07T13:28:05ZS. Schulzsschulz@cit-ec.uni-bielefeld.de
<p>It would be nice to have a brief example for callAsync() rpc calls (c++ and probably all others).</p>
<p>Just a short code snippet like for normal rpc calls but with the async case:<br /><a class="external" href="http://docs.cor-lab.org/rsb-manual/trunk/html/examples-basic.html#remote-procedure-calls">http://docs.cor-lab.org/rsb-manual/trunk/html/examples-basic.html#remote-procedure-calls</a></p>
<p>a good example could be a timeout for a rpc call.<br />i found it out on my own but it would have saved me some time (and others as well)</p> Enhancement #1727 (Closed): Update and test Spread plugin(s) to Spread 4.4 https://code.cor-lab.de/issues/17272014-01-27T10:32:32ZS. Wredeswrede@cor-lab.uni-bielefeld.de
<p>Spread 4.4 has just been released and contains some interesting features (less overhead for small messages, new protocol for highest performance, improved windows build system):</p>
<pre>
Available for download from here: http://www.spread.org/download.html
Spread 4.4.0 RC1 http://www.spread.org
Spread Concepts LLC is happy to announce the release of a
new release candidate version, 4.4.0 RC1, of the Spread toolkit.
The Spread 4.4 release is an important release that incorporates a new,
accelerated ring protocol. This protocol is tailored for data center networks
and can provide 30%-50% higher throughput and 20-35% lower latency in modern
local area networks This version also supports Spread's old ring protocol.
A new AcceleratedRing parameter has been added to Spread's configuration file.
If this parameter is set to true, then the accelerated ring protocol will be used.
If it is set to false, then the old ring protocol will be used. If it is left
unspecified, then Spread will try to determine which protocol is likely better for
your environment. If your configuration looks like it might be a LAN (i.e. - all
daemon IPs are in the same /16 network) rather than a WAN, then Spread will use
the accelerated protocol. Otherwise, it will use the original protocol. All the
daemons in a configuration must use the same ring protocol. Daemons with different
protocols will refuse to communicate with one another.
A new AcceleratedWindow parameter, with a value between 0 and the value of the
PersonalWindow parameter, should be specified as a flow control parameter in the
spread.conf file. The higher the parameter the more acceleration is expected --
up to a point. The sample.spread.conf file included in this release has
example settings for these parameters that enable the Accelerated Ring
protocol, as well as a description of their functions.
The main new features of this release are:
1) Accelerated Ring protocol to improve both throughput and latency in local area networks.
2) Redesigned message-packing, reducing overhead for small messages.
3) Updated MSVS project files for Windows source builds.
4) Several bugfixes that make Spread less likely to exit under high loss.
5) Expanded and improved logging.
For details check the Readme.txt file.
This release does not include any API changes, so applications should
be able to be relinked or recompiled with the new Spread library without
changes.
The Spread toolkit provides a high performance messaging service
that is resilient to faults across local and wide area networks.
Spread functions as a unified message bus for distributed applications,
and provides highly tuned application-level multicast, group communication,
and point to point support. Spread services range from reliable messaging
to fully ordered messages with virtual synchrony delivery guarantees, even in case
of computer failures and network partitions.
</pre>
<p>We should check whether these changes impose any problems and update our packages / plugins accordingly. This could also pose an opportunity to introduce plugins to the Java library.</p> Enhancement #1711 (Resolved): Change CLI to provide SVN/git-like subcommands for different taskshttps://code.cor-lab.de/issues/17112013-12-23T19:40:27ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
<p>Sub-commands identified so far:</p>
<ul>
<li>info</li>
<li>logger</li>
<li>send</li>
<li>call</li>
<li>introspect</li>
</ul>
<p>Potential future sub-commands:</p>
<ul>
<li>bridge</li>
<li>timesync</li>
<li>server</li>
<li>shell/repl</li>
</ul> Enhancement #1710 (Resolved): Change CLI to provide SVN/git-like subcommands for different taskshttps://code.cor-lab.de/issues/17102013-12-23T19:39:15ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
Tasks identified so far:
<ul>
<li>info</li>
<li>record</li>
<li>play</li>
<li>cat</li>
<li>transform (formerly merge)</li>
</ul>
Potential future tasks:
<ul>
<li>server</li>
<li>shell/repl</li>
</ul> Enhancement #1636 (Rejected): Check python multiprocessinghttps://code.cor-lab.de/issues/16362013-09-25T08:52:46ZAnonymous
<p>Check python multiprocessing to make use of multiple processors in rsb-python.</p>
<ul>
<li><a href="http://docs.python.org/2/library/multiprocessing.html" class="external">python multiprocessing</a></li>
<li><a href="http://www.slideshare.net/pvergain/multiprocessing-with-python-presentation" class="external">Presentation Slides</a></li>
</ul> Enhancement #1247 (Resolved): Remove singleton backwards compatibility for factorieshttps://code.cor-lab.de/issues/12472012-11-19T21:53:54ZJ. Wienkejwienke@techfak.uni-bielefeld.de
<p>This was introduced and marked as deprecated to force users to convert to the new api.</p> Enhancement #1025 (Resolved): Add Transport classhttps://code.cor-lab.de/issues/10252012-06-25T12:48:49ZJ. Moringenjmoringe@cor-lab.uni-bielefeld.de
The new <code>Transport</code> class would represent properties of transport as a whole (e.g. Spread, socket, inprocess),
<ul>
<li>Instances should aggregate the respective factory objects (in-push, in-pull, out, etc.)</li>
<li>Some Connector properties such as schema list could be moved into the new <code>Transport</code> class</li>
</ul>