>>>>> "Chris" == cbitmead <firstname.lastname@example.org> writes:
Chris> In article <email@example.com> firstname.lastname@example.org
Chris> (Janet Bell) writes: I don't know much about cgi
Chris> programing. Do you have to run a separate script for every
Chris> Until the scheme48 implementation is improved, 1.4 Meg has
Chris> to be loaded on every invocation. If this is buffered in
Chris> memory due to frequent access, then maybe it's not too bad,
Chris> but I suspect it's going to be a bit too slow for you.
Of course you can make a scsh server. The actual cgibins would then be small
C programms that just pass their argv and env to the scsh server. The server
would just fork a new scsh to do the job. In the future the scshserver could
even just fork a thread. The possibility to pass file descriptors to scsh
(not yet possible) would make the whole thing trivial.