"Nitin Shukla" <nitinshukla@infotech.stph.net> writes:
> How does apache handle multiple users? Does Apache create multiple instances
> of mod_dav for a each user or keeps only one instance of mod_dav per user.
The Apache server assigns a separate httpd child process to handle
each incoming client connection. Each child process is a clone of the
parent, running its own copy of mod_dav.
"Nitin Shukla" <nitinshukla@infotech.stph.net> writes:
> I am interested in adding my plug-ins between the mod_dav module of Apache
> and the mod_dav_svn module of Subversion. I am particularly interested in
> passing the "request_rec" structure to my application from the mod_dav
> module before it is passed to the mod_dav_svn module of Subversion. Can
> anyone help or give an idea of flow of webdav request from the mod_dav to
> the mod_dav_svn. It would be appreciable if one can give any url or document
> worth reading. Even if one can list the bunch of apis where I would be
> looking for will be appreciable. I am relatively new to the Subversion
> source code.
Nitin: these are all questions about Apache's architecture, not really
about Subversion. You need to either read the Apache documentation,
or buy yourself a book about how to write Apache modules. (I really
like the one from O'Reilly.)
The reason Subversion uses Apache as a server is so that we don't have
to think about any of these issues. Apache automatically manages
child processes, does authentication, ssl, compression, and has a
whole system for writing your own authentication modules. All of this
is tangential to mod_dav, and Subversion's use of mod_dav.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 20 15:09:55 2002