<br><br><div class="gmail_quote">On Wed, Jun 27, 2012 at 1:45 PM, Chris Cunnington <span dir="ltr"><<a href="mailto:smalltalktelevision@gmail.com" target="_blank">smalltalktelevision@gmail.com</a>></span> wrote:</div>
<div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Why would you do this? Perhaps to save resources like RAM. Instead of having a Unix process per user you have a Smalltalk process per user. Or users could share a common class side persistence. Or to have one VNC connection for several applications. Most likely, because you cannot resist trying it out.</blockquote>
<div><br></div><div>Nice! This might also be useful for live updates to a web application. Instead of loading code updates abruptly, as we do now, we could load the new version of the app into a separate environment. New sessions would be directed to the new environment, and existing sessions would continue to use the old environment. Once all the sessions expire, the old environment gets removed.</div>
<div><br></div><div>Colin</div><div><br></div><div> </div></div>