>Apache has an easy install msi on windows, and as long as the ports
dont
>conflict between IIS and Apache there are no issues.
>
>We have IIS for some stuff, Apache2 for svn and Apache1.3 for some
other
>programs all running together on a single server. no nightmares.
Apache2
>is configured as a proxy server for the other two so access to other
>urls isn't confused with :portnumbers.
>
>I see the advantage of an IIS ISAPI plugin where a company has a
particular
>policy on running IIS. But running Apache2 and IIS together needn't be
>difficult.
Agree that if you are an experienced admin on apache and know your way
around the config file then it would not be a nightmare. But what
happens
if you have only one fixed ip address and you are running a website of
iis
using both port 80 and 443 and also want to run subversion using the
WebDAV
network layer so that it is accessible for any user who's firewall
allows them to browse the internet. Which means that apache needs to run
on
port 80 or 443. This is a bit more complex than the freedom of your
solution
where you can just change the port number.
The need does exists for an IIS ISAPI plug-in not only for companies
that has
a particular policy on running on IIS but also to other new comers
(specifically ones from the a Microsoft background) to easily integrate
their current solutions with subversion and by doing so expose them to
the
true freedom of open source.
Gideon
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 5 14:42:19 2004