Long time ago, in a mailing list far-far away...
Somebody had done an Apache-perl-Squeak gateway hack to allow running
CGI scripts in Squeak. That was before there was PWS/Swikis.

WebTalk (by Tim Jones <tim at thregecy.com>)
ftp://st.cs.uiuc.edu/Smalltalk/Squeak/Applications/Webtalk/

It has webtalk.pl.cgi file. Honest: don't know what for... :)

WebTalk and another server, Webserver, were precursors to PWS

Webserver (by Georg Gollmann <gollmann at edvz.tuwien.ac.at>)
ftp://st.cs.uiuc.edu/Smalltalk/Squeak/Applications/Webserver/

The code above is perhaps old. You probably should check with
developers. But you could also take the perl script above, and make it
work with PWS.


Bolot


On Tue, 8 Jun 1999, David Farber wrote:

> 
> i think the answer the original poster wants to hear is that there is
> some way for swiki to work under CGI; i.e. instead of binding to a
> port it gets HTTP requests and posts HTTP responses through the CGI
> framework, just like any other CGI script would do. 
> 
> has anyone built a squeak-CGI interface? this would be incredibly
> useful. 
> 
> as for ISPs willing to host a swiki, i just happen to run a small web
> hosting service. (virtual hosting only, no dialup.) the problem with
> something like a swiki (at least for me) isn't so much security as it
> would be resource usage. how much memory does each swiki image need?
> one swiki probably wouldn't be that big a deal, but what if i had 10
> people who wanted to run swikis? with all ten in memory sitting around
> and listening to ports, i am sure that my poor server's memory would
> be totally maxed. 
> 
> david
> 
>