Re:[certi-dev] When should a constraint federate receive RO message?

[address@hidden]

---------- Initial Header -----------

From      :
address@hidden
To          : address@hidden
Cc          : 
Date      : Sun, 22 Jun 2008 14:15:38 +0200
Subject : [certi-dev] When should a constraint federate
receive RO  message?

Hi Eric,?

I think the described behaviour is ok. When a constrained
federate
want to receive ro message outside a TAR it have to enable the
asynchronous delivery switch.

Exactly

I think the standard says that a federate is constrained
directly after
invoking the enableTimeConstrained service.

( Perhaps anyone can verify the behaviour with another RTI
implementation. )

I used exactly the same "protocol" with the RTI NG. Certi
seems to follow the
same behaviour than RTI NG regarding EAD, ETC and TCE.

This means if a federate want to receive the callback TCE it
have to
call EnableAsyncDeliv before ticking for TCE.

Yes.

That's why I called enableAsnyDeliv directly after
enableTimeCon.





-- 
CERTI-Devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/certi-devel


Martin


---------------------- ALICE N°1 de la RELATION CLIENT 2008*--------------------
Découvrez vite l'offre exclusive ALICE BOX! En cliquant ici 
http://abonnement.aliceadsl.fr Offre soumise à conditions.*Source : TNS SOFRES 
/ BEARING POINT. Secteur Fournisseur d.Accès Internet