On 26.06.2010, at 19:02, Lawson English wrote:
> On 6/26/10 9:23 AM, Robert Krahn wrote:
>> Hi, Lawson --
>> 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.
>> A while ago we created a simple chat app:
>> Lively is still run by Apache but under
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 http://localhost:8080
"). 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.
> the nice thing about seaside is that I can use it as a one-click install
> localhost server and use server-side squeak code to interact with the
> Second Life client and server: use the webpage as an interface for the
> squeak code injecting data packets for SL.
That's hardly specific to Seaside, any Squeak web server would allow that.
- Bert -