[Seaside] VW, Seaside, CGIs and Apache
Colin Putney
cputney at wiresong.ca
Sun May 8 01:19:19 CEST 2005
On May 7, 2005, at 3:26 PM, Guenther Schmidt wrote:
> I'm just touching base with seaside.
>
> One question upfront:
>
> Is it possible to develop a WebApp using Seaside and VW and then
> deploying it as a binary CGI to run on Apache/Linux (x86)?
No. There are many reasons for this, but the most important, in my
view, is that Seaside needs to maintain state in between HTTP requests.
A CGI is launched anew with every request. For Seaside to run as a CGI,
it would have to save and restore the state between requests, and
maintain consistency in the case of concurrent requests. That would be
complicated, error prone, and probably too slow.
Seaside generally runs as a backend to a webserver written in
Smalltalk, such as Comanche, Swazoo or VisualWave. Some people also run
Apache as a font-end proxy/load balancer.
HTH,
Colin
More information about the Seaside
mailing list