[REBOL] Re: About FastCGI
From: petr:krenzelok:trz:cz at: 2-Jul-2001 17:00
Allen Kamp wrote:
> Could you submit a complete test example please? I am yet to be able to get
> it working on Windows. I keep getting "aborted: read failed" errors.
>
> I really wish windows worked in compatibility mode, how much simpler it
> seems.
>
Yes, you have to wait a little bit, while I am downloading our IS databases thru
parallel cabel to my notebook ... the typing is so o o s l oooow :-)
Anyway - I would like to see the most fine-tuned set-up. And it seems to me it
would be something like FastCGIExternalServer set-up, multiplexed tcp/ip
connection, ability of central rebol app to load-balance requests (by launching
another instances of rebol), something like internetworked rugby servers and
clients :-) We can't afford to wait few secs till ODBC 'insert request stops
blocking the request. The e-business test solution which I am after is -
Apache <--> Rebolcmd (fastcgi dynamic, not external) <-firewall-> Rebolcmd
<-directory or database spooler-> <--> AppServer <-database->
OK, so copying finished, let's get back to Apache setup ... First, however - you
are not alone having problems. The same Apache config as under Linux and it
works in differently:
LoadModule fastcgi_module modules/mod_fastcgi.dll
if you use ClearModules directive, you have to define AddModule .....
mod_fastcgi.c or something like that I was told ... (not the case with my setup)
<Location "c:/local-www/cgi-bin">
AddHandler fastcgi-script .fcgi
</Location>
... and - that's all. I can see however, that none of my rebol.cmd instances
(servers) remain to be persistent, while on Linux, the do. I also experimented
with FastCgiIpcDir \\.\pipe\fastcgi directive, but no success. I am not sure, if
it even works in dynamic mode, as docs say, that the directive must preceede
FastCGIServer (static, I don't want to use static setup), or
FastCgiExternalServer ... if you are experimenting with pipes, be carefull and
choose directory, where you have user permissions to write, and also be carefull
of using default temp directory, as it can be periodically deleted by some other
task, and it will break your fastcgi communication ....
Let me know if you find anything new regarding FastCgi usage ...
Thanks a lot ...
-pekr-