[CalendarServer-changes] [2929] CalendarServer/trunk/twistedcaldav/notify.py

[source_changes at macosforge.org]

Revision: 2929
          http://trac.macosforge.org/projects/calendarserver/changeset/2929
Author:   sagen at apple.com
Date:     2008-09-02 16:14:45 -0700 (Tue, 02 Sep 2008)
Log Message:
-----------
Update to comment

Modified Paths:
--------------
    CalendarServer/trunk/twistedcaldav/notify.py

Modified: CalendarServer/trunk/twistedcaldav/notify.py
===================================================================
--- CalendarServer/trunk/twistedcaldav/notify.py	2008-09-02 21:20:37 UTC (rev 2928)
+++ CalendarServer/trunk/twistedcaldav/notify.py	2008-09-02 23:14:45 UTC (rev 2929)
@@ -468,15 +468,17 @@
     create the node and then go through the configuration process,
     followed by a publish retry.
 
-    For monitoring purposes, you can specify a "TestJID" value in
-    the config file; XMPPNotifier will send error messages to that
+    For monitoring purposes, you can subscribe to the server's JID
+    as long as your own JID matches the "AllowedJIDs" pattern(s) in
+    the config file; XMPPNotifier will send error messages to your
     JID.  If you also want to receive non-error, debug messages,
     send the calendar server JID the message, "debug on".  Send
-    "help" for other commands.  Note, XMPPNotifier doesn't yet
-    handle registration or roster management, so you'll need to set
-    up the JID accounts out-of-band, using another XMPP client, for
-    example.
+    "help" for other commands.
 
+    To let clients know that the notifications from the calendar server
+    are still flowing, a "heartbeat" node is published to every 30
+    minutes (configurable).
+
     """
 
     implements(INotifier)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/calendarserver-changes/attachments/20080902/f0cfa781/attachment-0001.html