[CalendarServer-changes] [4659] CalendarServer/trunk/doc/Admin/ExtendedLogItems.txt

source_changes at macosforge.org source_changes at macosforge.org
Wed Oct 28 17:26:44 PDT 2009


Revision: 4659
          http://trac.macosforge.org/projects/calendarserver/changeset/4659
Author:   wsanchez at apple.com
Date:     2009-10-28 17:26:43 -0700 (Wed, 28 Oct 2009)
Log Message:
-----------
ReSTify

Modified Paths:
--------------
    CalendarServer/trunk/doc/Admin/ExtendedLogItems.txt

Modified: CalendarServer/trunk/doc/Admin/ExtendedLogItems.txt
===================================================================
--- CalendarServer/trunk/doc/Admin/ExtendedLogItems.txt	2009-10-29 00:22:03 UTC (rev 4658)
+++ CalendarServer/trunk/doc/Admin/ExtendedLogItems.txt	2009-10-29 00:26:43 UTC (rev 4659)
@@ -19,36 +19,50 @@
 
 These keys are always emitted:
 
- * ``i`` - the port number of the server instance emitting the log
-   entry.
+  ``i``
 
- * ``t`` - the amount of time spent processing the request (in
-   milliseconds).
+    the port number of the server instance emitting the log
 
- * ``or`` - the number of outstanding requests enqueued for the server
-   instance emitting the log entry.
+  ``t``
 
+    the amount of time spent processing the request (in milliseconds).
+
+  ``or``
+
+    the number of outstanding requests enqueued for the server
+    instance emitting the log entry.
+
 Keys that may be emitted depending on the client request and server
 response include:
 
- * ``rcount`` - the number of resources specified in a ``MULTIGET``
-   request.
+  ``rcount``
 
- * ``responses`` - the number of responses included in a
-   ``multi-status`` response to a ``PROPFIND`` request or a CalDAV
-   ``calendar-query`` request.
+    the number of resources specified in a ``MULTIGET`` request.
 
- * ``recipients`` - the number of recipients in a CalDAV scheduling
-   request via ``POST`` (which are typically only free/busy requests).
+  ``responses``
 
- * ``itip.requests`` - the number of attendees in a scheduling
-   operation triggered by an Organizer.
+    the number of responses included in a ``multi-status`` response to
+    a ``PROPFIND`` request or a CalDAV ``calendar-query`` request.
 
- * ``itip.refreshes`` - the number of attendee refreshes completed
-   after a scheduling operation.
+  ``recipients``
 
- * ``itip.reply`` - Either ``reply`` or ``cancel`` depending on...???
+    the number of recipients in a CalDAV scheduling request via
+    ``POST`` (which are typically only free/busy requests).
 
+  ``itip.requests``
+
+    the number of attendees in a scheduling operation triggered by an
+    Organizer.
+
+  ``itip.refreshes``
+
+    the number of attendee refreshes completed after a scheduling
+    operation.
+
+  ``itip.reply``
+
+    Either ``reply`` or ``cancel`` depending on...???
+
 In the following example, we see a ``CalDAV:calendar-multiget``
 ``REPORT`` for 32 resources in a user's calendar, which was handled by
 instance ``8459`` in 183.0ms, with one outstanding request (the one
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/calendarserver-changes/attachments/20091028/f5c8536c/attachment.html>


More information about the calendarserver-changes mailing list