Re: CGIs with OSX
Re: CGIs with OSX
- Subject: Re: CGIs with OSX
- From: T&B <email@hidden>
- Date: Mon, 2 Apr 2001 18:16:32 +1000
- is "postedFormData" part of the Unix Shell "language?"
No, it's just the variable I assigned. Note the "read postedFormData"
line which takes the data from the form, in this form
"formField1=value1& formField2=value2& etc". To then give the value
stored in the variable to the osascript line in the shell script, you
prefix the variable with a $.
Perl uses the%ENV data wrapper. "postedFormData" seems too simple and,
well, un-Unix-like in its intuitiveness.
There may be better ways, but I'm just trying to pass the form field
values at this stage, in the simplest way to simplify the exercise. My
AppelScript script takes care of unparsing it etc.
- when the Applescript CGI returns the full HTTP response, who does it
return
it to? It wouldn't know to return it to Apache. Is that what the "|
echo" is
for?
Yes, the echo takes care of this. The shell script outputs any echo
commands back to apache for the web page that the CGI produces. You need
the normal http headers etc, that are already produced by AppleScript
CGIs.
- the Applescript CGI expects a whole slew of environmental variable
(see the
Standard Additions dictionary). Will not receiving them cause errors?
You can pass these from the shell script. I was just simplifying. If you
open the test-cgi shell script in the CGI executeables folder, you can
see them and modify to pass them to your AppelScript script.
W*API onto Apache. Any takers?
I'm only dealing with existing AppleScript CGI scripts and trying to set
up a shell script to pass the form data to it in the form they expect.
Nothing to do with W*API CGIs, though there may be some overlap.
Why is 6.08 on an SE snappier than OSX on a Pismo 500?
Because Apple just wants to show off their gigaflop ;-)
Tom
T&B