Re: how do you use it?

"Jason P Sage" <[email protected]>
Newsgroups gmane.comp.web.fastcgi.devel
Organization Jegas
Message-ID <003601c6af91$0d749260$0201a8c0@dev01>
Generally speaking, from what I THINK I know so far - not having actually
used FAST CGI itself - but CGI programming for a long time (that's why I'm
interested in it) ... FASTCGI gives you a place to have a little daemon
running - that can manage its own database connections, handle its own
method of dealing with multi-tasking - whether a superb multiplexer or a
multi-threaded and/or parallel processing engine - that basically handles
ALL the DATA in and OUT from the HTTPD server. (Saves a lot of overhead
starting command shells etc - require to launch a standalone cgi app.

This being said, it is probably safe to assume you - the developer are
responsible for all the COOKIE code and Passing data back and forth etc.

Its not that hard if you know the formats - I'm not master - but for basic
html and forms and variables, and cookies, URI and sessions and all that
jazz - I've got it pretty well down... but non-html requests - I need to
study - e.g. file xfers. 

In short - with FASTCGI (correct me if I'm wrong anybody) you should be able
to do all that stuff - but you need to write the code yourself to handle it.

I tried to learn the formats from all those RFC or whatever specifications
that are out there - but I learned more from writing an app that acted like
a browser and showed me raw output from various web sites. I also learned
from looking at code other people wrote.

Once I understood the formats and what the headers are (basically TEXT with
predefined keywords etc) - Its became easier to write for.

I basically have routines that return valid headers for going out - but just
supplying the variable data, and coming in - I have a very mechanical way to
dissect any CGI request.... (HTML/form application encoded I think its
called)

Anyway - you have to write that stuff your self likely.

Jason P Sage


-----Original Message-----
From: fastcgi-developers-bounces+jasonpsage=jegas.com-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
[mailto:fastcgi-developers-bounces+jasonpsage=jegas.com-xGejAJT2w6xVgU18Zptdi8XXUOn6P5/[email protected]]
On Behalf Of Tom Allison
Sent: Monday, July 24, 2006 9:40 PM
To: fastcgi-developers-xGejAJT2w6yOE5Ap4OspEtHuzzzSOjJt@public.gmane.org
Subject: [FASTCGI] how do you use it?

I'm kind of perplexed here so I'll ask the stupid questions.

When I use perl and call for a CGI module, I get with it all kinds of really

cool abilities related to %ENV and STDIN/STDOUT and the ability to even set 
cookies...

I can't find much of anything about what FCGI/FastCGI offers in terms of
methods 
or properties that are similar..

Is it correct to assume that FCGI doesn't do any of this and if I'm
interested 
in any kind of CGI related functionality (headers, cookies, %ENV...) then I 
should probably just load the CGI modules?

similarly under ruby I should load fcgi, cgi, cgi/cookie, cgi/session rather

than expecting any of this kind of insight into the HTTP process from the
FCGI 
working environment?  (please don't take any of these negative questions to
be a 
slight on FCGI/FastCGI

It's a stupid question but I would feel stupider if I found I was loading 
multiple modules when only one was required.  I haven't really found
anything 
that tells me that fcgi does other than some rudimentary examples.  (or is
it 
that simple and I'm just trying to make it complicated?)
___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/



-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.3/395 - Release Date: 7/21/2006


___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.