<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi, Lawson --<br><br>If you only want to process certain requests with Seaside it is not necessary to serve the LK files with it because Apache is much better suited doing this.<br><br>Example:<br>A while ago we created a simple chat app: <a href="http://lively-kernel.org/repository/webwerkstatt/BWINF/chat-prototype.xhtml">http://lively-kernel.org/repository/webwerkstatt/BWINF/chat-prototype.xhtml</a><br><br>Lively is still run by Apache but under <a href="http://lively-kernel.org/web-collab-squeak">http://lively-kernel.org/web-collab-squeak</a> we process POST requests to implement the chat's login/logout/broadcasting logic. The URL is transformed by a Apache proxy rule so that it reaches the Squeak server ("ProxyPass /web-collab-squeak <a href="http://localhost:8080">http://localhost:8080</a>"). By the way, in Squeak we didn't use Seaside but the good old KomHttpServer (Andreas Raab's WebClient framework would now probably be a good alternative) since Seaside would be overkill for such a simple task.<div><br></div><div>Best,</div><div>Robert<br><br><div><br><div><div>On Jun 26, 2010, at 1:57 PM, Lawson English wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 6/26/10 3:47 AM, Bert Freudenberg wrote:<br><blockquote type="cite">On 26.06.2010, at 09:54, Lawson English wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">The title says it all. It seems perfectly doable on its face, but I'm<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">not sure how to get started.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"> From the server's point of view, LK is just a bunch of files. They get downloaded when running LK, and uploaded when saving. You can use Seaside to serve them, sure, but it's overkill.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote>Thanks. I was pretty sure that was the case, but not positive. The idea <br>(for now) is to create a standalone, one-click seaside server with LK <br>interface that I can use to experiment with Second Life interfacing <br>without having to do much by way of widget creation. The <a href="http://scriptali.us">scriptali.us</a> <br>controls often seem not to work as I'd like, and I am hoping that <br>localhost-served LK will provide an easy way to create control panels <br>on-the-fly.<br><br><br><blockquote type="cite">You should figure out first what you want the Seaside app to do. For regular LK, all the logic is performed client-side. You do not need complex server-side logic, which is what Seaside is good at. A "dumb" server is totally sufficient.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote>Sure, but the logic would come from the messages passed back to the <br>server, as always.<br><br><br><blockquote type="cite">If you want to learn how to serve files using Seaside, that has nothing to do with LK itself. So please ask on the Seaside mailing list, not here.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote>Thanks for your response.<br><br><br>Lawson<br><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></div></body></html>