Medium Flame:Re: fPCGI vs. Windows 2003 ==>> bottom post

[Fairlight]

In the relative spacial/temporal region of Mon, Jun 07, 2004 at 02:09:44PM
-0500, Tony Freehauf achieved the spontaneous generation of the following:

> First let me say that I have found for 25 years filepro people are great,
> this is no knock of them.  I fail to understand why there is not a
> informational source with notes on tricks & special solutions. I mean the
> number one advertised Server, Windows 2003, we should all have available
> the needed information to make filepro & us look good?  I think fptech
> sould have run it & published notes on implimentation for the developers.

It's not a filePro issue, Tony.  It's a Windows issue.  Specifically
something in either Server 2003 or IIS 6.0, or a combination thereof.  This
is specific to the CGI environment, and fPCGI as a product notwithstanding,
that's not fP-Tech's fault.

Given the -exact- same server (W2K3/IIS6), -any- software running through
IIS would encounter this issue.

The problem and responsibility isn't fP-Tech's, it's Microsoft's.  And
their uhm..."Knowledge Base" apparently doesn't cover this, despite the
fact they maintain one after a fashion.

This is like trying to hold fP-Tech or the fP community responsible for the
development decisions of RH, SCO, Apache, etc.  It's just not their
problem, and no amount of testing they could have done would -fix- the fact
that Mickeysoft managed to break their own software again.  All they could
do is put a warning out.  M$ needs to fix it.

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html