[kwlug-disc] Massage Passing stuffs?

Keefer Rourke mail at krourke.org
Thu Sep 14 07:18:06 EDT 2017


I would look into option 3 with dbus.

From Wikipedia:
> In computing, D-Bus, a software bus, is an inter-process communication and remote procedure call mechanism that allows communication between multiple computer programs concurrently running on the same machine.


On September 14, 2017 12:18:37 AM EDT, William Park via kwlug-disc <kwlug-disc at kwlug.org> wrote:
>I posted this to GTALUG, so my apology if you've seen it before.
>I'm posting to KWLUG, because there may be more "robotic" people here.
>
>I have various peripherals that I need to read and write.  At the
>moment, they are all local and don't need to talk to each other.  I
>think of 3 approaches from top of my head:
>
>   1. Use select(2) (and friends) to round-robin the peripherals.  This
>    is "classic".
>
>   2. Each peripheral is serviced by a separate thread, and main thread
>    does the business logics.
>
>  /3/. Each peripheral is serviced by a separate process, and they pass
>    "messages".  This option is what I want to investigate.
>
>So, do you know any "message-passing" scheme, framework, or library
>that
>I can look up?

-- 
Regards,
Keefer C. Rourke

Sent from my Android device with K-9 Mail. Please excuse my brevity.




More information about the kwlug-disc mailing list