<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi, Lawson --<div><br></div><div>We just improved loading. The first access to a world will be slow, afterwards a cached version of the code base is used and access should be faster. Please note that we only implemented this for the wiki (e.g. <a href="http://lively-kernel.org/repository/lively-wiki/sandbox/sandbox.xhtml">http://lively-kernel.org/repository/lively-wiki/sandbox/sandbox.xhtml</a>).</div><div><br></div><div>Best,</div><div>Robert</div><div><br></div><div><a href="http://www.lively-kernel.org/repository/webwerkstatt/issues/110209_NetworkUsesOldModelCode.xhtml"></a><br><div><div>On Feb 9, 2011, at 10:58 PM, Lawson English wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>I realize that this is a work in progress, but the download speeds for <br>viewing even the simplest example page are incredibly slow. Is there any <br>work being done to cache at least some of the library so you don't have <br>to download the entire library with every page? Even the backbutton ont <br>eh browser seems to take about as long as the first access. This is <br>totally unacceptable, even as a demo.<br><br>Also, have you compared the speed of running LK in local host vs getting <br>it from a remote server?  I can think of plenty of places where having a <br>localhost webpage acting as a GUI for a regular application (e.g. MMORPG <br>game client) would be useful.<br><br>Lawson<br>_______________________________________________<br>lively-kernel mailing list<br><a href="mailto:lively-kernel@hpi.uni-potsdam.de">lively-kernel@hpi.uni-potsdam.de</a><br>http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel<br></div></blockquote></div><br></div></body></html>