Re: Beginners Question

Jason P Sage wrote:

Email is fine - I'm just surprised and happy kind of - that my
"difficulties" are the same as others - and that I'm not the first

So am I. I "feel" that you became intrigued by the RAMDRIVE thing.

To run into this stuff - and that its validation I MIGHT be on the right
track - based on your response about the CGI-win thing and the files.

I ran in the past with the tiny CGI model but we didnt had at that time
a high level of demand.

What I'm doing, I'm sure you understand - is that little CGI script - I'm
hoping - runs just fine getting slammed - at least in Linux. I'm not done
researching - and I got to go for now BUT - I'm staying the course - I'm
staying with the idea of a "COMMON" programming API so I can get cracking on
real stuff faster - I mean I have the SAME "cgi calls" in my source code for

For both STRAIGHT CGI APP, and the STUB - so I can write code for both at
the same time.

In my case, the CGI and now the API are "frozen". I simply did them in
the past and nowadays I dont change them anymore.

All the comercial stuff is done outside, on those tasks. So the
development environment is a single one. The common developer doesnt
need to know these issues. He/she are focused on the html page only.

If I stay with that idea - and later decide I'm to slow - then making an
interface to FastCGI directly or writing an Apache Module would be easier -
and the main code would already be tested... kinda like software - plug and
play.

I do have to go - but I'm saving your email if that is ok with you :)

No problem. We're pursuing the same goal !

Jason - Have a great day and good luck to you.

Thank you.

(I'm here to bang ideas off too via email for now I think is fine)
See Ya Jose!

OK.

-----Original Message-----
From: fastcgi-developers-bounces+jasonpsage=jegas.com-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
[ mailto:fastcgi-developers-bounces+jasonpsage=jegas.com-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org ]
On Behalf Of Jose Adriano Baltieri
Sent: Wednesday, July 12, 2006 12:32 PM
To: fastcgi-developers-xGejAJT2w6yOE5Ap4OspEtHuzzzSOjJt@public.gmane.org
Subject: Re: [FASTCGI] Beginners Question

Jason P Sage wrote:

Hi JOSE! Cool - that's what my first response - thanks for feedback from
your experience also!

Apache is Cool .. I use it - but I would also check out www.lighttpd.net

(It has definitely caught my eye)

I don't know that much yet - but - that web server is free like apache, is
in many linux distributions - and seems geared toward "lean and mean"

which

is what I like. I'm using apache right now for my stuff at home, and

regular

CGI and/or PHP for little things.

Now I have a question. When you did the whole RAMDRIVE thing - was that
Windows or Unix/Linux?

Windows.

Did you make a tiny stub CGI program to talk to a different process? Did

it

do badly?

As a matter of fact, the tiny CGI was there only to "fake" the
web-server. By that time, I used CGI-WIN, which is a protocol that
creates a INI file with the variables. Then, the CGI-WIN is supposed to
generate another file back, with the html response.

What I did in my case was this : let the CGI-WIN create the file and,
make it WAIT for the answer then EXIT.

On the other hand, the "real" application is monitoring or watching that
RAMDRIVE folder. When a file "bubles up" in there, it takes it to be
processed right away.

It turned out that I had the file being processed even BEFORE the CGI
were started (because who creates the INI file is the HTTP server itself
- it creates the file and then lauches the external process, that is,
the CGI).

Got it ?

Also - You mentioned writing a HTTP server yourself - well.. my biggest
biggest fear - SSL. Trying to get SSL into my own homemade server so that
It would work with Verisign, or others...

EXACTLY WHAT WORRIES ME TOO ! So many coincidences !

Otherwise - writing a web server for hosted applications on a different

port

along side a traditional web server makes sense to me - but not without

SSL.

(Writing the TCP/IP stack and multi-task and/or process processing is no
weekend project either)

Definitively. Needs to be completely reliable.

Any ways - I'd be really curious about your responses - who knows what we
might stumble across with ideas :)

Where are you talking from ?

If you want, we may exchange some thoughts through Skype - not voice but
chatting. Let me know.

See ya later
Jason P Sage

-----Original Message-----
From: Jose Adriano Baltieri [ mailto:jabaltie-a/[email protected] ]
Sent: Wednesday, July 12, 2006 10:28 AM
To: Jason P Sage
Subject: Re: [FASTCGI] Beginners Question

Jason P Sage wrote:

Hello Jason !

We have many similarities : as a matter of fact, I'm not MultiThreaded.
I'm MultiTasked. Also, I'm also getting my data from a Unisys mainframe.
And I'm also thinking about writing my own http server but, I'm afraid
of doing it. Too much responsibility.

Moreover, I also worked in the past with a tiny CGI, just like you did.
By that time, I had done a very little CGI in C that would only dump the
request and wait for the answer. But, you still have the overhead of a
process start/end per request. This is too much more than it's size, I
think. I left that CGI exe on a RAMDRIVE too.

Other than that, I'm also kind of "lost" cause I still have to learn
Apache and then FASTCGI.

Thanks for your attention !

--
Obrigado,
------------------------------------------------------------------------------
Jose Adriano Baltieri - Analista de Sistemas
DTI - CENTRO - UNIMEP - Universidade Metodista de Piracicaba
PIRACICABA - SP - Brasil - Fone : (19) 3124-1858
------------------------------------------------------------------------------

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/