[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [certi-dev] When should a constraint federate receive RO message?
From: |
Pierre Siron |
Subject: |
Re: [certi-dev] When should a constraint federate receive RO message? |
Date: |
Mon, 07 Jul 2008 15:42:35 +0200 |
User-agent: |
Thunderbird 2.0.0.5 (X11/20070719) |
Christian Stenzel a écrit :
> 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.
>
> 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. )
>
> This means if a federate want to receive the callback TCE it have to
> call EnableAsyncDeliv before ticking for TCE.
>
> That's why I called enableAsnyDeliv directly after enableTimeCon.
>
>
>
>
>
>
Hello,
maybe we should tick in the billiard code for these callbacks.
My two questions:
1°) I do not find again the classification of the callbacks in TSO, RO
and Commands.
So, if the timeConstrainedEnabled is a command, the side effect disappears.
2°) The CERTI implementation of enableTimeRegulation should be modified.
It must be treated as a timeAdvanceRequestAvailable, this is like a time
advancing
state where the RO messages are delivered.
There are less problems for the enableTimeConstrained service than for
the enableTimeRegulation service.
A bientôt,
Pierre
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [certi-dev] When should a constraint federate receive RO message?,
Pierre Siron <=