in reply to text file w/o CGI

Update: davorg posts a nearly identical question above. I'd given up in frustration and posted mine before seeing his. The only value this ads is option (C) below.

spunkcell, it's time to clarify something.

When you say "I can't use CGI on this server," do you mean

A. I am not allowed to use CGI scripts, or
B. I am not allowed to use CGI.pm
People above seemed to have assumed one of these or the other, leading two vastly divergent opinions on how to address your problem.

Or do you mean

C. I am not allowed to use my own CGIs, and must use the ones that are already present.

Replies are listed 'Best First'.
Re: (dws - clarify!)Re: text file w/o CGI
by spunkcell (Initiate) on Apr 05, 2001 at 21:43 UTC
    Wow, you guys are great.
    I admit I'm not sure if I can't use the CGI.pm or are not allowed to use CGI scripts.
    Here is our email coversation;
    ME to their cto-
    "I'm the programmer that will be working with Scott and Ryan on the CBOT investors floor tutorial. I'll be setting up our test box today and was wondering which version of Solaris you use. I also would like to know which web languages we can use on your servers in the finished version (PHP, Perl, etc.)."
    Him-
    "solaris 2.7 and perl would be the only choice BUT we don't run it as a CGI and will not allow CGI access from the outside. What were you thinking of doing? Just curious..."
    Hope that can clear things up some, I really apreciate everyone's help.
      The CTO has told you what they don't allow, but he hasn't told you what they do allow. Note the word "allow". It suggests "policy", and policies can often be influenced (i.e., changed) in response to business needs. If your business need involves adding dynamic web content to their web server, and they don't allow that, then this may need to get escalated to (I'm guessing) the sponsor of the "CBOT investors floor" project so that they can influence policy at a higher level (e.g., by negotiating with the CTO or the CTO's boss).

      A good next step is to explain to the CTO what your project needs are, and ask him to suggest options. This puts him in the position of working with you, rather than blocking you. He's already given you the opening by asking what you're trying to accomplish. Take that opening.

        If spunky has accurately portrayed the enviroment they have to work in (ie, Vignette), turning to perl to do something so simple is outright silly when Vignette already provides the tools to do so.

            --k.


        Very wise.
        Thank you.