Skip to content
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

Closed
DeepDiver1975 opened this issue Nov 19, 2013 · 10 comments
Closed

Unify WebDav, CalDAV and CardDav entrypoints #5939

DeepDiver1975 opened this issue Nov 19, 2013 · 10 comments
Labels
enhancement overview p2-high Escalation, on top of current planning, release blocker
Milestone

Comments

@DeepDiver1975
Copy link
Member

** reminder for myself and @jancborchardt **

some more explanation here from @evert - see #4951 (comment)

Hey guys,

I am at CalConnect, which is the tri-yearly meetup for the internet calendaring standards organization. We do testing between a bunch of different vendors, and as I'm representing sabredav, I also get questions about owncloud.

One of the things that was mentioned was the fact that owncloud exposes 2 separate endpoints for cal- and carddav. Specifically for some clients that support both these protocols, it can be a bit confusing as there are also 2 principal urls.

I think it would be good to combine both endpoints into one. I imagine it should be relatively easy, as you just need to make sure that calendars and addressbooks are in both trees, and all plugins are loaded for both endpoints.

That way you also don't have to break the existing urls.

I feel this is a better design, and will provide better compatibility as clients get more advanced.

@karlitschek
Copy link
Contributor

Not sure why this is important.

@jancborchardt
Copy link
Member

So that

  • other apps can also make use of the unified addresses – so that there can be other calendar and contacts apps
  • the addresses can be shorter, which is really important for when you need to punch it in on a mobile phone

More reasons @DeepDiver1975?

@DeepDiver1975
Copy link
Member Author

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.

@DeepDiver1975
Copy link
Member Author

In addition with respect to the requirements to implement proper DAV permissions we need to restructure the root webdav element anyhow:
https://github.com/fruux/sabre-dav/wiki/Sabre-DAVACL-Plugin

@jancborchardt
Copy link
Member

Is this related or even a duplicate of #4951? cc @evert

@evert
Copy link

evert commented Dec 11, 2013

sounds like a duplicate to me!

@zkvvoob
Copy link

zkvvoob commented May 28, 2014

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?

@simonbuehler
Copy link

on a side note:
could the urls be shortenen somehow, its really hard to enter that long urls twice on a smartphone, thx

@DeepDiver1975
Copy link
Member Author

basically done -> closing

@PVince81 PVince81 added p1-urgent Critical issue, need to consider hotfix with just that issue p2-high Escalation, on top of current planning, release blocker and removed p1-urgent Critical issue, need to consider hotfix with just that issue labels Dec 11, 2015
@lock
Copy link

lock bot commented Aug 7, 2019

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.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement overview p2-high Escalation, on top of current planning, release blocker
Projects
None yet
Development

No branches or pull requests

7 participants