Hi, On Fri, May 08, 2026 at 20:48:15 CEST, Spencer via users wrote: > Is there a formal distinction between a blocking RPC and a > non-blocking one, other than the expected time that will be taken?
That's the heart of it. A (remote) procedure call is synchronous and returns only after the called (remote) procedure decides to return. The differentiated consideration of "blocking" vs. "non-blocking" RPCs stems from our experience with services like the timer. Norman mentioned this and it's also documented in Foundations https://genode.org/documentation/genode-foundations/25.05/architecture/Inter-component_communication.html#Synchronous_remote_procedure_calls__RPC_ https://genode.org/documentation/genode-foundations/25.05/architecture/Inter-component_communication.html#Asynchronous_notifications The underlying RPC mechanism is the same but the semantics of the service interfaces pledge limited blocking time. Regards -- Christian Helmuth Genode Labs https://www.genode-labs.com/ · https://genode.org/ https://floss.social/@genode · https://genodians.org/ https://de.linkedin.com/company/genodelabs Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Archived at https://lists.genode.org/mailman3/hyperkitty/list/[email protected]/message/KGCJJZX2SCX4BXDO4LIMVA4B46FUCD3I/
