<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div><br></div><div>I'm currently working on so-colled proc_mobility behavior. It is a prat of my thesis which aims to add agent migration to eXAT platform. proc_mobility doesn't depend on eXAT platform so can be used in whatever you want. Here is link to the repository <a href="https://github.com/michalwski/proc_mobility/tree/over_tcp">https://github.com/michalwski/proc_mobility/tree/over_tcp</a>. The brach "over_tcp" has more features than master. Unfortunately I haven't write any documentation so far, so feel free to ask if you think that proc_mobility can be useful.</div><div><br></div><div>Best regards,</div><div>Michał Piotrowski</div><div><br><div><div>On Jul 31, 2012, at 2:29 PM, Tyron Zerafa wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hello everyone,<div> Does Erlang support process migration? Meaning, is there a way in which I can stop a running process (A) on one node and resume it on another completely different node? </div><div>If this is not supported, one way to go around it is to extract the process state before suspending it and somehow inject it into the new process on the remote node. Does Erlang provide such functionality?</div>
<div><br></div><div>Any tips and suggestions on how one can extract/ inject the process state from/ into processes?</div><div><br></div><div>- Thanks in advance</div>
_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote></div><br></div></body></html>