RE: cgi

new topic     » goto parent     » topic index » view thread      » older message » newer message

Sorry,
By the time I read your message I had it working.  The
puts is ESSENTIAL to the cgi.  All my headaches were
because the webserver I chose to test my cgi out with
didn't properly support a binary win32 cgi.  Switching
to Xitami fixed this.

STDIN and STDOUT are usually the screen.  But if a
webserver is calling the program (rather than
dos/windows) the STDIN/OUT should travel between the
client browser and the webserver.  Did that make any
sense?  I spent a week learning the basics of cgi so I
could do this, and all the while I had the code right,
but the webserver couldn't handle it properly :x
-=Cassidy=-
--- Kat <gertie at PELL.NET> wrote:
> 
> On 12 Oct 2001, at 13:51, Ryan Johnson wrote:
> 
> > 
> > I don't understand cgi, but I was thinking about
> trying it one of these 
> > days...
> > Anyway, although I don't know cgi, I do know that
> from my experience, 
> > when you run a euphoria program (in windows), it
> does not create a 
> > prompt window unless it needs to.
> > Correct me if I'm wrong, but when you use "puts(1,
> "text")", doesn't "1" 
> > represent the screen? And when you put to the
> screen, Euphoria creates a 
> > console window so it can "puts" to it.
> 
> Which is why i asked if Cassidy had tried commenting
> out that line, hinting 
> that all the puts(1,..) lines should be commented
> out. But no one replied. The 
> dos and win stdout can't be redirected, cept thru
> dos's ">" and "|" batch 
> commands, or i could be wrong again.....
> 
> Kat
> 
>
> 
>
> 


=====

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu