I've wrapped your message to 75 characters-per-line.
On Tue, Feb 17, 2004 at 11:41:06AM -0600, Paul Welter wrote:
> 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?
Well, mod_dav + mod_dav_svn ~= 20,000 lines of intricate code. My guess
is whatever headache you're trying to avoid by not installing Apache will
be greatly outweighed by the headache you bring upon yourself by rewriting
mod_dav and mod_dav_svn.
Further, we're likely to make improvements in mod_dav_svn. You'll need
to make the same improvements to your reimplementation, and there are more
of us than there are of you, so you might have trouble just keeping up
with a diverging mod_dav_svn once you were done.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Feb 18 00:16:01 2004