I'm planning to rename the packages provided by the various httpd modules
so that there is no conflict with other packges (e.g., Don Libes cgi.tcl
also provides a "cgi" package, which is completely different.)

Ideally I would change all the code so Doc_Foo becomes doc::foo
or even httpd::doc::foo, but for the time being I'll keep the procedure
names the same.  Instead, this will just affect the various "package requires"
that are done during the startup sequence.

I'll probably add a "httpd_" to all the package names, except of course
for the core httpd package itself.  Comments?

Also in the plans is a cleaner way to add code to a distributed server
so you don't have to directly edit the startup code (what a concept!)

--      Brent Welch     <[EMAIL PROTECTED]>
        http://www.ajubasolutions.com
        Scriptics has become Ajuba Solutions


Reply via email to