On 12/11/2013 02:14 PM, Matthias Goldhoorn wrote:
Our policy is:
* stop the component
* reconfigure it via properties
* restart the component
In some special cases if there is no other way than changing
properties while the component is running the dynamic properties
should be used. Can you please point out why this is the case here?
That's only the porolicy for static configurations,
Dynamic properties were introducer where --- during runtime a
configuration change is allowed
For a Servo if your change your system design you might during runtime
change some allowed ranges.
The dynamic propertie is a stable solution and not a "spcial case".
Or did i miss something big here?
Matthias
We should avoid using dynamic properties if possible because every
dynamic property is adding a lot of complexity to the TaskContext source
code.
Try to use the KISS principle ;-):
/Keep it simple, stupid/
Alex
Alex
--
Dipl.-Ing. Alexander Duda
Unterwasserrobotik
Robotics Innovation Center
Hauptgeschäftsstelle Standort Bremen:
DFKI GmbH
Robotics Innovation Center
Robert-Hooke-Straße 1
28359 Bremen, Germany
Tel.: +49 421 178 45-6620
Zentrale: +49 421 178 45-0
Fax: +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen)
E-Mail: [email protected]
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
_______________________________________________
Rock-dev mailing list
[email protected]
http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
