[EMAIL PROTECTED] wrote:
Though I one 100% agree with the stance that a proper web server should..
well.. serve pages - It sure would be nice if we could have a logging
subsystem in apache 2.1 or higher which took care of some of the harder
things for us module/appserver developers when
[EMAIL PROTECTED] wrote:
Though I one 100% agree with the stance that a proper web server should..
well.. serve pages - It sure would be nice if we could have a logging
subsystem in apache 2.1 or higher which took care of some of the harder
things for us module/appserver developers
On Sat, 2 Mar 2002, Bill Stoddard wrote:
Wouldn't just making ap_log_error() ap_run_log_error() solve a lot of
these problems?
+1 - with perhaps something like an 'always pass through' Ie even if an
module provides an 'OK' it continues just as a 'DECLINE' so that certain
major failures can
[EMAIL PROTECTED] wrote:
Though I one 100% agree with the stance that a proper web server
should..
well.. serve pages - It sure would be nice if we could have a
logging
subsystem in apache 2.1 or higher which took care of some of the
harder
things for us module/appserver
On Sat, 2 Mar 2002, Ryan Bloom wrote:
[EMAIL PROTECTED] wrote:
Perhaps the logging module should be split up in the same way, with
mod_log handling the hooks, and mod_log_disk handling logging direct
to
disk, mod_log_sql handling direct to database, etc.
Wouldn't just making
Though I one 100% agree with the stance that a proper web server should..
well.. serve pages - It sure would be nice if we could have a logging
subsystem in apache 2.1 or higher which took care of some of the harder
things for us module/appserver developers when bouncing around
logging data.
