[Rock-dev] improvement TaskContext.get

[Sylvain Joyeux]

On 11/03/2011 04:17 PM, Sylvain Joyeux wrote:
>> What's bad with caching?
> If not done properly, it can hide that things changed. In the port case,
> you would start having a problem if the task unregisters a port and then
> re-registers a new one with the same name. It is actually not only
> possible, but problematic.
Correcting myself: it is actually *not* a problem.

Ports are referred to, through the CORBA layer, as (task_reference, 
port_name). So, in the case above, the port would still be valid

In another word, you do have the guarantee that the non-caching 
behaviour is exactly the same than the caching behaviour (would return 
objects that are equivalent)

In the nameservice case, if a new task associates itself with the new 
name, and the old one is still there, then

    non-caching: return the new task
    caching: return the old task

What I'm not sure of is if this difference in behaviour is a problem or not.
-- 
Sylvain Joyeux (Dr.Ing.)
Space & Security 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
-----------------------------------------------------------------------