-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Unify WebDav, CalDAV and CardDav entrypoints #5939
Comments
Not sure why this is important. |
So that
More reasons @DeepDiver1975? |
CalDAV and CardDav urls are as of today handled by the calendar and contacts apps. Because it's our main architecture principle to NOT depend on other apps as of today I could only reimplement all the *DAV code within my own app and have to export another dav url. The goal should be to move the caldav and carddav core mechanisms into ownCloud core and provide PUBLIC API to register adressbooks and calendars which can follow their own implementations. |
In addition with respect to the requirements to implement proper DAV permissions we need to restructure the root webdav element anyhow: |
sounds like a duplicate to me! |
Sorry, I posted a duplicate topic. Anyway, like I wrote on the forum, there's an Android app called DAV Droid which can sync both calendar and contacts, but currently this is only possible through adding two separate accounts which is not very pretty or convenient. It would be quite helpful if owncloud could give *DAV access via a common URL, something like example.com/cloud/remote.php/. And why not consider a future possibility for a single syncing app which would permit file access, as well as address book and calendar synchronisation? |
on a side note: |
basically done -> closing |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
** reminder for myself and @jancborchardt **
some more explanation here from @evert - see #4951 (comment)
The text was updated successfully, but these errors were encountered: