Wed 16 Feb 2011 11:56:50 AM UTC, comment #2:
Hi Eugene,
Thank you for your report.
I'll try to handle it with your help.
Your proposal for encoding/decoding is not complete
we should take care of endianity because those time value
may be sent accross the network between 2 hosts with different
endianity.
This is not that complicated to implement
we can mimic what is done in
RTI1516fedTime::encode(void* buffer, unsigned long bufferSize).
I'll try to do that myself (include the RTI1516TimeInterval class).
Concerning 1516 compliance you are right.
However I do not quite understand:
"But federate ambassador callbacks are still invoked with initial timestamp parameter value"
When you propose modification would you be able
to do it as a "patch file" (a diff file) ?
It is far easier to review/test.
Moreover if you have a federate test case please attach it
to the tracker too. We may use it to reproduce the error
and may b add it to our non-regression tests suite.
I'll post another comment when I've done the encoding part.
|