andrew at morphoss
May 19, 2012, 4:58 PM
Post #4 of 4
(287 views)
Permalink
|
On Fri, 2012-05-18 at 18:28 -0400, Bobby Krupczak wrote:
> Hi!
>
> > > (Just debugging 'put' operations gives me more logging than I would
> > > normally want. I was hoping to not have to read all the protocol
> > > specs.)
> >
> > Hi Bobby,
> >
> > You actually want to use the hook described here:
> >
> > http://wiki.davical.org/w/Configuration/hooks/log_caldav_action
>
> Thanks! Am I inferring correctly when I think that this already
> implemented as the following in my config file?
>
> $c->dbg['caldav'] = 1;
>
> That is, will I accomplish the same thing by simply enabling the about
> in my davical config file?
Quite different. The log_caldav_action is specifically about structured
logging (or processing) of the action of CREATE/UPDATE/DELETE of DAV
resources in a flexible way. The example solution is to log them to a
file, and can be used for (e.g.) applying the changes to another place,
or updating a static copy of a collection, etc., etc.
The:
$c->dbg = array( various things to enable debugging for);
is for debugging during development. The 'caldav' thing you have enabled
is primarily used for debugging some fairly high-level stuff and
preprocessing of the incoming request.
Cheers,
Andrew.
--
------------------------------------------------------------------------
andrew (AT) morphoss (DOT) com +64(272)DEBIAN
Dyslexia means never having to say that you're ysror.
------------------------------------------------------------------------
|
signature.asc
