[Xenomai-help] Uniqueness of registry objects

[Xenomai-help] Uniqueness of registry objects

[Thomas.Debes]

Hi,

I am using the native skin together with mutexes and message queues. If
I use the same name for both objects (mutex="test" , queuename="test") I
can not register the second one because it fails with error -17 (file
exists) in rt_queue_create. I assume that the registry service doesn't
make a difference between the various RT object types. Can you confirm
this behaviour? If it is by design would it be better to differ between
the various RT object types (mutex, queue, pipe etc.)?

Thanks
Thomas 

MAN Roland Druckmaschinen AG
Vorsitzender des Aufsichtsrates: Hanno C. Fiedler
Vorstand: Gerd Finkbeiner (Vorsitzender), Dr. Ingo Koch, Dr. Markus Rall, Paul Steidle    
Sitz der Gesellschaft: Offenbach am Main, Registergericht: Amtsgericht Offenbach HRB-Nr. 42592    
USt-Ident-Nr. DE 250200933

Re: [Xenomai-help] Uniqueness of registry objects

[Philippe Gerum]

Thomas.Debes@domain.hid wrote:
> Hi,
> 
> I am using the native skin together with mutexes and message queues. If
> I use the same name for both objects (mutex="test" , queuename="test") I
> can not register the second one because it fails with error -17 (file
> exists) in rt_queue_create. I assume that the registry service doesn't
> make a difference between the various RT object types. Can you confirm
> this behaviour?

Yes.

 If it is by design would it be better to differ between
> the various RT object types (mutex, queue, pipe etc.)?
>

This uniqueness was deliberately required so that we could implement
remote object registration in the future, for supporting distributed
systems. In such a case, it's better that peers do not have to know
about each other's exact nature. In this case, one would just want to
establish a link between peers based on a common protocol, regardless of
what actually implements each communication endpoint.

-- 
Philippe.