Re: [certi-dev] Bug fixing

[Yaomin Fu]

Hi Eric,

Sorry for late reply. I am off doing other things, and will back to rti
sometime
late.

I'll do the patch once having time.

I have tested CERTI with JSAF, using rti-s. Generally it works well, but
sometimes has abnormal behavior. I will ask our JSAF expert to do a
sanity test
late and will inform you the result.

During the "DLC" enabling, what I feel is that to be real DLC, having a
specification is not sufficient, something at the implementation level need to
be coordinated. Perhaps that not a specification can do.

For instance, the JSAF uses a RTIFedTime class exposed from rtis. It happens
CERTI has RTIFedTime class with very similar method signature. Thus, I can
easily make CERTI DLC enabled (implementing SISO DLC), with minor chance, to
replace rtis, and make it work with JSAF.

Note that the RTIFedTime class is not part of specification. It just
implements
the FedTime interface and provides extra methods to ease the use of FedTime
object.  If a rti implements the FedTime interface in another way, then there
is no chance to make it work with JSAF, not even possible to be DLC,
unless add
to the top of it a wrapping class.

MAK RTI covers this issue by prompting their implementation of the HLA
interface
specification. They have a VR-Link product which allow to dynamically
connect to
any rti if it has implemented the DLC specification. But the users have to pay
for using their VR-Link to build federates.

I think having a rti code base like yours is a good place to prompt a generic
implementation.

Quoting Eric Noulard <address@hidden>:

> 2009/12/16 Eric Noulard <address@hidden>:
> > Hi Yaomin,
> >
> > Thank you for your feedback.
> > I'll try to give you an update on this in 2-3 days I'm kind of busy
> > just now.
> > (anyone wanting to take over during this is time is welcome :-)
>
> Hi Yaomin,
>
> I'm afraid it took me more than expected to dig this issue :-(
> I did file a bug report:
>
> https://savannah.nongnu.org/bugs/?29032
>
> I think we really need to add a network message for this to work properly.
> However, I should polish some other issues first before trying to handle
> this issue.
>
> Is this bug blocking you ?
> If it is blocking you would get a chance to provide a patch?
>
> I know you already made a proposal embedded in a mail but I'd rather
> use a proper tool generated patch.
>
> You can do this like this:
>
> A) With CVS access
>
> 1) do an anonymous cvs checkout
> 2) make the modifications you propose tinto the source code
> 3) generate a patch using
>      cvs diff -u
>    (or equivalent command from tool like TortoiseCVS, Eclipse
> etc...or other tool you
>     may be using to access CVS)
>
> B) Without CVS access.
>     Unzip a pristine CERTI Source tree
>     Copy (or unzip a second) pristine CERTI Source tree
>
>     Make your modification in either tree and compute the diff
>     between the two trees in "unified diff" format using a diff tool.
>
> Send the patch to the list or attach the patch to he tracker:
> https://savannah.nongnu.org/bugs/?29032
>
> By the way where are you in your try for using CERTI with JSAF?
> --
> Erk
> Membre de l'April - « promouvoir et défendre le logiciel libre » -
> http://www.april.org
>
>
> --
> CERTI-Devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/certi-devel