Re: [Paparazzi-devel] Paparazzi bus MQ wrapper

[Felix Ruess]

Hi,

I would be in favour of trying to create some sort of abstract pprzbus that can have multiple backends...

The difficult part is really finding an appropriate API for this and what paradigm it should use.

i.e. message based pub/sub or something like ivy?

Right now you are using redis in basically the same way as Ivy, the pprzbus layer has no idea about the message definitions.

Meaning you also end up with just string representations of the message in redis (just like on the Ivy bus).

I'm not really convinced that this makes that much sense in the end.

I don't quite understand the addition of a paramter to filter on sender. Why did you add that?

Cheers, Felix

On Wed, Jan 28, 2015 at 2:03 PM, Alexandre Bustico <address@hidden> wrote:

Le 28/01/2015 13:09, Gerard Toonstra a écrit :

  * The regex is executed against each received message in each process, which eventually becomes CPU
    intensive and laggy.

On this specific point, it's not. regexp filtering is done on the emitter side, just once time by regexp : even if
several agents bind the same regexp (exactly the same, it's implemented as a hashtable, key is regexp,
value is list of agents which bein the regexp). only filtered results are sent over network.


--
Alexandre


_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel