[Seaside] Re: VW, Seaside, CGIs and Apache

[Guenther Schmidt]

Colin,

thanks, for clarifying that, I had hoped the answer wouldn't be no.

However I'm still not 100% certain that it can't be done somehow. True, the CGI would have to be kept alive between request, at least for as long as there are valid sessions (600 seconds timeout). I'm not sure that can't be done, even though I don't have a clue how (yet).

Günther

Colin Putney wrote:
> 
> 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