Open georgehrke opened 8 years ago
cc @LukasReschke
this way any webcal is only available in the web app - I'd expect them in any connected caldav client as well. can subscription help us with this respect?
As far as I understood CalDAV subscriptions its only meant to store the actual link and not the objects itself. Is this wrong?
As far as I understood CalDAV subscriptions its only meant to store the actual link and not the objects itself. Is this wrong?
I was hoping you already know more about this :sob: :wink:
it's already pretty hard to find some documentation about it. Can you link me to the standard?
According to this sabre file it's only a list.
Searching the web for CalDAV managed subscriptions
or "{http://apple.com/ns/ical/}refresh rate"
didn't turn up anything useful :confused:
I begin to question this standard's existence :sob:
Although this still doesn't explain whether or not the server is supposed to cache the objects or if it's really just a list of subscriptions
Maybe @evert can enlighten us :laughing:
It's just a list of subscriptions. Although a server-side cache might be cool =)
I don't think a spec exists. I believe I just reverse-engineered it.
I don't think a spec exists.
Haha, that explains a lot :see_no_evil:
Thx a lot :)
@DeepDiver1975 For now I'll implement webcal in the client only as planned for 1.1.
If anything caching webcal and propagating them to clients as ordinary calendars would go into ownCloud 9.1.
What would be used as encryption key if we were to encrypt the local storage saved calendars ?
in addition to: https://github.com/owncloud/calendar/issues/132
cache (not password protected) webcal subscriptions using HTML5 Browser Storage.
needs discussion about security: