-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Event attendance should be backed by DAV #2425
Comments
@chibenwa : so we should be able to advertize multiple DAV urls with discovery endpoint correct? Separated let's say by commas? Or was it a copy/paste mistake, cause I don't see the point... one should be enough as it is the same dav system in the end. Like:
Or just:
After confirmation I will create the task on the backend backlog :) |
No, it is a mistake on my side. We shall advertize link to OpenPaaS backend AND the DAV URL... |
@hoangdat Do we have a design that has it yet? |
Closed in favor of #2425 . No DAV invovled. The design would be the same as today with OpenPaaS invites OpenPaaS. We just need to add a |
Docs: |
@hoangdat @tddang-linagora fix regarding this issue deployed on staging. Please test again and tell us if it resolves your blocking point or not. Thanks |
Why
Do like blue bar in OpenPaaS INBOX.
Exact synch between calendar and TMail.
No longer rely on HTML parsing...
Summary
https://dav.linagora.com
https://openpaas.linagora.com
Request breakdown
Same creds than Tmail shall be used with the DAV server.
Request 1: Get the OpenPaaS identifier
Request 2: fron the `` header lookup the event on the calendar
Request 3: Manage participant status
Copy the JSON, patch participation status for only the local user (here btellier "partstat":"ACCEPTED" -> "partstat":"TENTATIVE")
Note: the self link can be obtained by parsing the event above (href).
TODO
The text was updated successfully, but these errors were encountered: