Skip to content

Commit 866e141

Browse files
committed
Document iMIP API change for 26
Signed-off-by: Anna Larch <anna@nextcloud.com>
1 parent 252868b commit 866e141

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

developer_manual/digging_deeper/groupware/calendar.rst

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -161,6 +161,27 @@ Calendars that only return `ICalendar` are implicitly read-only. If your app's c
161161
162162
}
163163
164+
Handling iMIP data
165+
~~~~~~~~~~~~~~~~~~
166+
167+
You may implement the ``IHandleIMipMessage`` interface to process iMIP data you receive in a client and want to pass on for processing to the backend.
168+
169+
Please be aware that there are some security considerations to take into account. You can find more infomation on these and the conditions that have to be fulfilled for iMIP data to be processed in the `RFC <https://www.rfc-editor.org/rfc/rfc6047>`_
170+
171+
.. code-block:: php
172+
173+
<?php
174+
175+
use OCP\Calendar\IHandleIMipMessage;
176+
177+
class HandleIMipMessage implements IHandleIMipMessage {
178+
179+
public function handleIMipMessage(string $name, string $calendarData): void {
180+
// Validation and write to your calendar representation
181+
}
182+
183+
}
184+
164185
Resources
165186
---------
166187

0 commit comments

Comments
 (0)