-
Notifications
You must be signed in to change notification settings - Fork 43
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
Cache webcal calendars in browser's local storage #364
Comments
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? |
I was hoping you already know more about this 😭 😉 |
it's already pretty hard to find some documentation about it. |
According to this sabre file it's only a list. Searching the web for I begin to question this standard's existence 😭 |
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 😆 |
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. |
Haha, that explains a lot 🙈 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: #132
cache (not password protected) webcal subscriptions using HTML5 Browser Storage.
needs discussion about security:
The text was updated successfully, but these errors were encountered: