Nice title...
in my setup, i have a parent process with multiple children with IDs, lets say the are named child_1 to child_3.
the parent recievces messages with an ID and should forward it to the child with the corresponding ID. Therefore all children announce the same service, lets say "child_communcation", to the parent.
In order to avoid ambiguities, the parent process would have to reconfigure its route every time a message arrives. that means if message with ID 3 arrives, the route for the service "child_communication" must lead to child_3.
this solution seems odd to me, am i missing a mechanism in genode that allows a parent to communicate with its children directly, when they all announced the same service?
regards David
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.cl... _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main