Would a complete ABI refactor decouple messaging, I.e. Telemetry would be just another message subscriber, and datalink/telecommand would be just another message publisher?
Is ABI logically equivalent to an object request broker (eg as might be found in an RTOS), except unrolled at compile time rather than using a runtime component (bus or middleware)?
Chris Gough
On 26/08/2012, at 6:10 PM, Christophe De Wagter <address@hidden> wrote:
This would make more distributed computing possible pushing the ABI messages over a bus like CAN which are also publish subscribe.
On Saturday, August 25, 2012, Gautier Hattenberger wrote:
Yes, it could be a replacement to the sensor event functions that
are in the main.c files. We need to see if it really makes things
easier to integrate and if the performance are acceptable.
bingo, that's exactly what I was asking about. I saw the recent
commit/merge and didn't understand the changes. I actually found
that link after asking, sorry I should have looked harder first.
Is the general idea to eventually replace all internal
message access with callbacks (in the airborne code)?
Chris Gough
Le 25/08/2012 07:57, Luiz
Flavio Felizardo a écrit :
Or maybe application
binary interface.
On Sat, Aug 25, 2012 at 2:56 AM,
Luiz Flavio Felizardo <address@hidden>
wrote:
I
don't know where did u get that from but it certainly
can stand for Aviation Business International.