The ISAPI connector has been somewhat unloved over the past few years.
We're recommending Apache 2 over IIS to all our customers, so if that's 
widespread it'd explain the lack of interest.
 
I've been submitting patches from our local branch over the past year, trying 
to improve some aspects of it (still waiting for the next dev branch to add 
chunked encoding support).
I've also updated some of the docs to mention features that have been there for 
years (i.e. isapi_redirect.properties).
The only other person I've seen touch the IIS code in recent memory is Mladen.
 
Binary JTC builds from Jakarta have always been a bit hit and miss - I build 
all ours locally.
The only IIS6 issue I know of is that you have to add a web services extension 
for the redirector for it to work - new locked down IIS rules or something.
 
tim

________________________________

From: Preston L. Bannister [mailto:[EMAIL PROTECTED]
Sent: Mon 12/12/2005 21:35
To: [email protected]
Subject: Who is working on the ISAPI connector code?



After downloading the isapi_redirect.dll 1.2.15, found the VERSIONINFO
contains 1.2.14 (and "1.2.14dev"), which is going to confuse the heck out of
our support folks (when the code reaches the field).  Downloaded and
recompiled 1.2.15 after updating the version information, and in the process
noticed the DSP file is slightly dorked (it should be "isapi_redirect.dsp"
to fit MSVC conventions).  At the same time we are having trouble getting
isapi_redirect.dll to work on IIS6 (Windows 2003 Server), and a decided lack
of clues.  I did follow up on the hints offered by others with the same
problem - no luck (so far).

Then there are the three very lightweight properties files - one file would
be simpler.

Looks like I might be in the position to want to make minor changes to the
isapi_redirect code.  I may still have commit access (from long ago), but
don't want to be stepping on any toes.  Who - if anyone - is working on the
connector code, or claims ownership?



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to