<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div>On 03 Mar 2016, at 12:17 AM, Éric Pailleau wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr">And for local pidname, a simple put() can store the spawned Pid in parent process dictionary and retrieve with get().</p>
<div class="gmail_quote">Le 2 mars 2016 11:12 PM, Éric Pailleau <<a href="mailto:eric.pailleau@wanadoo.fr">eric.pailleau@wanadoo.fr</a>> a écrit :<br type="attribution"><blockquote class="quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><p dir="ltr">Hi,<br>
Could not this be solved by spawn_priv/x functions ? I mean functions that do same than spawn/x but spawned process accept only messages from parent process ?<br>
No need to change things in process registry then.<br>
</p>
</blockquote></div></blockquote></div>Good luck supporting/debugging the code that may register itself, but able to receive messages only from the process that spawned it.<div>Did April 1st arrived early this year?</div><div><br></div><div><div></div></div></div></body></html>