|
|
Posted by comp.lang.php on 11/24/08 11:28
Steve wrote:
> > A bit more of an explanation. What do you mean by "interactive or
> > batch"?
>
> Can it just be given a chunk of data and get on with it's job, or does
> it have an interactive conversation with the user, with several round
> trips from client to server before it can do it's thing?
>
Ok thank you. Those are terms that I as a web developer am not used to
hearing, so it threw me.
> I suppose the question is: does it have to be a web-facing CGI script
> at all, could it be coded as a simple command-line script
> (#!/usr/bin/tcl) taking command-line args and returning the result to
> STDOUT; it could then live outside the web directory tree and be
> protected from abuse from the internet. No need for any fancy
> authentication then.
>
I couldn't run the script as a standalone command-line script because
the scripts are hosted on a remote site and I do not have privileges
outside of my account which resides within the framework of the
document root. It is a single back-end batch processing script that
must exist within CGI because CGI, as well as the user, are within the
group that has the privilege to access a group-accessible XML file
(this cannot be altered as it is set up by the hosting provider across
the board for all users on his hosting service).
Phil
> ---
> Steve
Navigation:
[Reply to this message]
|