Re: [certi-dev] CERTI RTIG Best Effort connection from RTIG to RTIA

[Pierre Siron]

Dear Alexander,
with the (very) first versions of CERTI, it was possible to use TCP or UDP
with a great simplification: All the communications were TCP or UDP,
that is to say all the attributes were reliable or best effort.

We coull have another problem: Some communications must be reliable,
the internal communications of the RTI, NULL messages for the time management
for example.

Today we are using CERTI only with TCP.
I do not know the amount of work to do for the reactivation and upgrade
of the best effort communications.
Sorry for this answer.
We are looking for some help to do this task.

Best regards,
bien cordialement,
Pierre

Le 13/07/2015 14:51, address@hidden a écrit :

Hello,

we’ve encountered the following problem: rather than relying on a reliable connection (TCP) we want to use a best effort connection for the communication of RTIG with the federates (RTIA).

Changing the FOM Model form “reliable” to “best effort” didn’t do the trick (every communication is via TCP) so we had a look at the source code and as far as we could see it, RTIG is never really sending anything via UDP.

 

In the RTIG.cc exection-method there is this line

  link = socketServer.getActiveSocket(&fd);

where link is now used as a TCP-Socket and that never changes (or we are simply blind).

 

The question is: how can we establish a UDP/Best Effort connection from RTIG to RTIA or is that not possible?

 

In use: Certi 3.4.2.

 

Best regards,

Alexander