<div>Possibly. Is that the only way to go... is OTP the answer</div>
<div>or is there another paradigm/behaviour/pattern that works</div>
<div>for these situations. Hot code loading is one of the reasons</div>
<div>I like Erlang and quite often my processes crash because</div>
<div>of dependencies on the old code. <br><br> </div>
<div><span class="gmail_quote">On 7/9/07, <b class="gmail_sendername">jm</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><a href="mailto:email@example.com">firstname.lastname@example.org</a> wrote:<br>> hi,<br>><br>> what is the best way to do design a system for live code update?
<br>> in theory, i would like to ship a tar/bundle/etc with all the necessary<br>> code. the end user should be able to load that while the system<br>> is running and then proceed as thogh nothing much has changed.
<br>><br>> this should be similar to a live code update that was done on the<br>> network gear that erlang ran on.<br>><br>> how does one structure their project to accomplish this?<br><br><br><br><br>If you don't mind the blind leading the blind...There's a section in
<br>"OTP Design Principles" (<br><a href="http://www.erlang.org/doc/pdf/design_principles.pdf">http://www.erlang.org/doc/pdf/design_principles.pdf</a> ) that covers<br>releases starts around page 46.<br><a href="http://www.trapexit.org/index.php/Building_An_OTP_Application">
http://www.trapexit.org/index.php/Building_An_OTP_Application</a> also has a<br>section on releases. I've done niether myself though. Is this what your<br>referring to or some finer point I've missed?<br><br><br>Jeff.
<br>_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:email@example.com">firstname.lastname@example.org</a><br><a href="http://www.erlang.org/mailman/listinfo/erlang-questions">