[CalendarServer-changes] [13579] CalendarServer/trunk/txdav/caldav/datastore/sql.py

source_changes at macosforge.org source_changes at macosforge.org
Fri May 30 12:51:37 PDT 2014


Revision: 13579
          http://trac.calendarserver.org//changeset/13579
Author:   cdaboo at apple.com
Date:     2014-05-30 12:51:37 -0700 (Fri, 30 May 2014)
Log Message:
-----------
Add comments.

Modified Paths:
--------------
    CalendarServer/trunk/txdav/caldav/datastore/sql.py

Modified: CalendarServer/trunk/txdav/caldav/datastore/sql.py
===================================================================
--- CalendarServer/trunk/txdav/caldav/datastore/sql.py	2014-05-30 18:44:16 UTC (rev 13578)
+++ CalendarServer/trunk/txdav/caldav/datastore/sql.py	2014-05-30 19:51:37 UTC (rev 13579)
@@ -4036,6 +4036,18 @@
         of their split copy - it should be identical, part from per-user data, so it will apply
         cleanly. We can include an X- headers to indicate the split R-ID so "smart" clients/servers
         can simply ignore this message.
+
+        @param onlyThis: if L{True} then only this L{CalendarObject} will be split (the organizer copy only),
+            if L{False}, then organizer and attendee copies are split (this is the normal behavior).
+        @type onlyThis: L{bool}
+        @param rid: the date-time where the split should occur. This needs to be a specific instance
+            date-time or L{None} to have one automatically determined. To determine a valid value,
+            given an arbitrary date-time, use the L{iCalSplitter.willSplit) method (which is used
+            in L{CalendarObject.splitAt}).
+        @type rid: L{DateTime}
+        @param olderUID: sets the iCalendar UID to be used in the new resource created during the split.
+            If L{None} a UUID is generated and used.
+        @type olderUID: L{str}
         """
 
         # First job is to grab a UID lock on this entire series of events
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/calendarserver-changes/attachments/20140530/f43ef158/attachment.html>


More information about the calendarserver-changes mailing list