[Seaside] Best way to embedding Seaside in static HTML?

Ruben Bakker ruben at mailplaneapp.com
Mon Jun 25 14:36:48 UTC 2007

Hi Sebastian,

Thanks for your answer.

Here are the reasons why I did the static stuff in RapidWeaver:
- I have designed the site with a graphical tool, supported by templates
etc. This is much easier than writing code and css by hand.
- The site is super robust, only apache need to run to serve all static
- The site is very fast and can absorb heavy load, seaside is only bothered
with the dynamic stuff
- No sessions, no timeouts for the static stuff

I have currently a couple of "wizards" that are dynamic. These are done in
seaside. My dream was to embed those into the static pages. Design,
navigation etc. are already there.

In GWT (Google Web Toolkit) or Wicket you can embed your components at a
specific point in HTML:

Here is a Wicket example, where the component is inserted as the contents of
the span element:

    <span wicket:id="message">Message goes here</span>

Does a similar functionality exist in Seaside? It would allow me to use the
static HTML and then embed my dynamic seaside components. These pages would
of course be controlled by Seaside to allow the rendering to work, back
button to work.

I hope this makes sense.

On 6/25/07, Sebastian Sastre <ssastre at seaswork.com> wrote:
>  Hi Ruben,
>     did you evaluate the option of doing it seaside based instead of
> static based?
>     I ask because, as far as I know, almost anything but seaside can
> handle the back button and for controlling that consistently you have to
> have a server to handle it consistently "behind the scenes". For the rest,
> is almos a mere fileserver (over http), a role that apache can handle very
> well.
>     my 2 cents,
> Sebastian Sastre
> PD: also as far as I know, most seaside apps are architected like that
>  ------------------------------
> *De:* seaside-bounces at lists.squeakfoundation.org [mailto:
> seaside-bounces at lists.squeakfoundation.org] *En nombre de *Ruben Bakker
> *Enviado el:* Lunes, 25 de Junio de 2007 10:38
> *Para:* seaside at lists.squeakfoundation.org
> *Asunto:* [Seaside] Best way to embedding Seaside in static HTML?
> I have some static pages (with navigation) etc. that are served by apache.
> These pages are designed and published with RapidWeaver. Seaside is used for
> some forms "inside" the static pages. Therefore I have setup apache to
> proxy/reverse proxy Seaside.
> The "embedding" is done with iFrames:
>      <div id="content">
>           <iframe name="target"
>                src="http://mysite.com/seaside/entry_point"
>                width="620"
>                height="500"
>                frameborder="0"
> scrolling="auto"
>                id="target"></iframe> <!-- End content -->
> It works. However, some users experience problems:
> - the back key doesn't work correctly
> - the seaside app is rendered after the static contents
> - some browsers don't support the iframe tag
> - Refresh the page doesn't refresh the iframe in some browsers
> Is there any better way to achieve the same goal? I know the opposite
> (seaside on the "outside") would work better, however I do have more static
> contents and want the static pages to perform as fast and as reliable as
> possible.
> Thanks for your help!
> --
> Ruben
> http://mailplaneapp.com
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20070625/f8e56c54/attachment.htm

More information about the Seaside mailing list