[Rock-dev] New ring-buffer connection policy in RTT

[Sylvain Joyeux]

RTT 2.6 (which is the current version in master) has a new buffer policy 
which is a ring-buffer, i.e. it will drop the oldest samples instead of 
the newest samples as we currently have.

Since this has been widely recognized as the "expected" buffer policy 
... I was wondering if we should switch to that by default when using 
:buffer.

The two integration plans would therefore IMO be:

1. Don't change anything
   - simply add a :ring_buffer policy type

2. Migrate to ring buffers by default
   - add both a :fifo_buffer and :ring_buffer policy types, where 
:fifo_buffer is the current policy
   - make the currently used :buffer an alias to :fifo_buffer
   - switch to having :buffer become :ring_buffer after a while

3. Switch to the new policy altogether
   - add a :fifo_buffer policy which points to the current buffer policy
   - make :buffer the ring buffer policy

Votes ?

-- 
Sylvain Joyeux (Dr.Ing.)
Senior Researcher

Space & Security Robotics
Underwater Robotics

!!! Achtung, neue Telefonnummer!!!

Standort Bremen:
DFKI GmbH
Robotics Innovation Center
Robert-Hooke-Straße 5
28359 Bremen, Germany

Phone: +49 (0)421 178-454136
Fax:   +49 (0)421 218-454150
E-Mail: robotik at dfki.de

Weitere Informationen: http://www.dfki.de/robotik
-----------------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
(Vorsitzender) Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.:    DE 148646973
Steuernummer:  19/673/0060/3
-----------------------------------------------------------------------