On Mon, Sep 30, 2002 at 05:35:40PM -0700, Ryan Morgan wrote: >... > This patch moves all the DAV method registration into the mod_dav module > from the http core. I'd like to do this for a couple reasons: > > 1) It makes more sense to register these methods from the same module > they are used in.
mod_dav is (currently) an optional module. However, those methods are defined within RFC standards. They apply to everything. > 2) Since Apache can only handle 62 registered methods, it doesn't make > sense to register these in the core even if the dav module isn't loaded. > (Other modules may need these slots in the method bitmask) There are no other HTTP methods in the current RFC universe. No other method has a "better" claim to those slots than the DAV methods. If you're going to have slots, then use them for standard methods. At the moment, those are the DAV methods. If/when we see an explosion of other methods, and the space getting crowded, *then* we can move them. >... > This patch also fixes a bug where DAV's BIND and SEARCH methods were being > registered with the core twice, since post_config gets called twice. > I have put in a check so that the methods only get registered once. Barely a bug. The core returns the same number for the second registration. > This passes the DAV litmus test (http://www.webdav.org/neon/litmus/), but > it could use some reviewing by people more familiar the module. > > Comments? I see little purpose for this. The DAV methods, which are defined by RFCs, are moving out for some nebulous concept of other "more righteous" methods. I just don't follow that reasoning :-) Cheers, -g -- Greg Stein, http://www.lyra.org/
