RE: subversion and IIS with asp.net
From: Paul Welter <pwelter_at_loresoft.com>
Date: 2004-02-17 18:41:06 CET
The proxy is an interesting idea. I could create an asp.net application to port forward 80 to whatever port Apache is installed on. The reason I would have to do it that way is for firewalls. These days, almost every company only allows traffic on port 80 and 443. Though this would still require the installation of Apache that I would like to avoid. As for emulating Apache, what format is a .so file? Can that be imported like a dll? I think this approach would require a keen understanding of Apache internals. I thinking it would be less work or at least work I have a better understanding for, to reproduce what mod_dav and mod_dav_svn do. Handling the http communications I'm not so worried about. The thing I need information about is how to forward the data streams from a .net world to the subversion library. I'm not even sure which library to call. I have noticed while poking through the source code that there is a bindings\com folder. This appears to be a COM binding to the subversion library but I can't find any information about it. Can someone point me to some more information about this? If this is what I think it is and it implements everything the subversion library does, then I could interface with the subversion library through the COM interface. Anyone have any insights to this?
From: Mark Benedetto King [mailto:email@example.com]
On Tue, Feb 17, 2004 at 09:57:22AM -0600, Paul Welter wrote:
The "easiest" approach I can think of would be to write a shim that sits
Why do you need to run subversion through IIS? Why not just proxy to
This is an archived mail posted to the Subversion Dev mailing list.