[Seaside] How to Implement a Website

Boris Popov boris at deepcovelabs.com
Mon Jul 2 01:43:12 UTC 2007

First rule of seaside club is to never optimize prematurely. Second rule of seaside club is to never optimize prematurely. In all seriousness one can already serve all resources with a plain web server, just dump them to disk when deploying and change resource URL on your root component to that location. Works great and let's you develop without apache, manage all files in source control system of choice etc.

Bookmarkable URLs are also possible, but its hard to get into much detail on a small keyboard, but there was plenty of talk on the list about it just a little while ago.

What I'm hinting at is this. Try to implement what you want in seaside and then check if you need to go the static route or not. Chances are you'll save yourself a lot of work :)


(Sent from a BlackBerry)

----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: Seaside - general discussion <seaside at lists.squeakfoundation.org>
Sent: Sun Jul 01 18:34:43 2007
Subject: Re: [Seaside] How to Implement a Website

Richard Eng wrote:
> Okay, as a Seaside/Squeak newbie, please forgive my stupid questions...
> How do I embed or redirect to a Seaside app from within static html content?
> I tried to find Boris' blog post concerning this but I was unsuccessful.
> I looked at "Best way to embedding Seaside in static HTML?" but the iframe
> technique seems problematic. The rest of the thread is over my head.
> Is there not a "best practice" recommendation for how to mix static html and
> Seaside components together? This would seem to me to be a common (the most
> common!) way to develop a website. As I understand it, you want static html
> to be served up by Apache for performance reasons, and Seaside for the
> actual application (business logic).
> And you want the Seaside app embedded within the static html content so that
> you have a consistent look and feel for the entire website. This has to be
> the canonical architecture for a website/web app, doesn't it?

I too think this would be a nice feature.

It seems that it would be nice to be able to generate an html page which
could be served by Apache or web server of choice which contains the
static html (parts) of a web page with possibly a JS controller for
making the call and inserting the dynamic (Seaside) parts.

This would seeming help in a couple of ways. Offloading truly static
pieces to a high performance web server, static html, images, css, etc.
But allow the truly dynamic web app part to be seaside. This would
seemingly help performance of a Seaside site, and provide a potentially
reasonable way to implement a RESTful/bookmarkable interface to a
Seaside site.

I am not yet learned enough to understand all the implications, if and
where it would limit are cause problems in a Seaside web app. Or to
implement a best practices way of doing this. But I am interesting in

I believe this is a good discussion to have. If there are issues or
problems cause by such an idea, hopefully they will be disclosed. If not
maybe an implementation come for at some point in the future.

Just some thoughts.

Seaside mailing list
Seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20070701/ea1dd9c6/attachment.htm

More information about the Seaside mailing list