[Seaside] Best way to embedding Seaside in static HTML?
ssastre at seaswork.com
Mon Jun 25 13:48:34 UTC 2007
did you evaluate the option of doing it seaside based instead of static
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,
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
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:
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
Thanks for your help!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Seaside