<div class="gmail_quote">On Thu, Dec 17, 2009 at 4:28 PM, Andreas Raab <span dir="ltr"><<a href="mailto:andreas.raab@gmx.de">andreas.raab@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Future messages allow you to use concurrency in cases where it would be very hard to synchronize with locks - in the above I would have to guard all the modifications of the scrollbar's value by some lock but using the future message allows us to introduce a level of concurrency that would be difficult to achieve otherwise.</blockquote>
<div><br></div><div>What is the scope of this safety with respect to shared state and mutation? Are you essentially treating the entire image as a vat (in the E sense)? Is it per morphic project? Or something else?</div>
<div><br></div><div>- Stephen </div></div>