On Tue, 23 Nov 1999, David Bovill wrote:
> > But you can also set them yourself (for example for a CGI) by just
> > putting the value into variables named $whatever prior to starting up
> > the CGI process. Note that this doesn't apply to MacOS which has no
> > concept of environment variables (CGI on the Mac is done with
> > AppleEvents instead).
>
> Isn't that just how WEBSTART ET AL DO IT. The information must be coming
> from the browser into the server socket, no?
Right, that's how it gets to the HTTP server.
> If so, then mchttpd does not have to use applevents surely?
I guess it depends on what you're trying to do. If you're trying to
explain how CGI programs typically work on the various platforms,
understanding stdio and environment variables (for Windows and UNIX)
and AppleEvents (for Mac) is important. I had the impression that
that's what your goal was.
If all you want to do is add custom handlers to mchttpd, the problem
is a lot simpler. Andu has come up with an idea where you can just
add a script to the message path with "start using" or "insert script"
and mchttpd can just call that handler if you get or post to a URL
that doesn't have an extension in its name. This will be a lot faster
and more efficient than the way CGI is done on the other platforms,
and immensely easier to debug. It's just not compatible with the way
it's done with other HTTP servers (though it is similar to the way
it's done on most Java-based servers).
Regards,
Scott
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
