Michal Podhradsky

> It is involved in that when `rust-mavlink` copies the messages to other ports things start falling apart whereas things work as expected when they're just sent directly via serial...

> Avoiding `mavlink-router`'s restrictions on UDP broadcast is one of the motivations of this project. We want to be able to broadcast to any number of ground station instances on...

Hi @wucke13 ! I thought about this library as "bare minimum" - i.e. it only provides struct definitions and a couple of convenience functions (socket and serial read for example)....

I just compiled it with nightly-2017-12-12, probably any other version of similar date will work. But I will give RLS a try too. @bruno-medeiros thanks for RustDT, it helped me...

@gautierhattenberger what do you think?

Default can be anything really, 1 is a good number, because 0 indicates "priority not set" which can be useful to know (e.g. when handling errors). It is a priority...

The use case I had in mind was to have the priority queue a part of the transport layer. See #70 - the queue is a part of the user...

The "default" priority is set at compilation time, but it can be changed on runtime if needed (see https://github.com/paparazzi/pprzlink/pull/70/files#diff-88c9c4ad71adde0ca53ec6beafc8750fR51 in #70 ), assuming the message handling code implements it. Although...

@gautierhattenberger any thoughts on this? This could be nicely used in user-defined transport (similar to https://github.com/paparazzi/paparazzi/commit/0e552b47cdab6458484aa0049f798df25085849b )

I like it to be a part of `check_space` - probably just adding a single argument will be sufficient. Will modify accordingly.