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.

Sign up for GitHub

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

Jump to bottom

Implement RFC6578 #9

Open
georgehrke opened this issue Aug 18, 2018 · 0 comments
Open

Implement RFC6578 #9

georgehrke opened this issue Aug 18, 2018 · 0 comments
Labels
enhancement New feature or request feature: CalDAV Related to CalDAV feature: CardDAV Related to CardDAV

Comments

@georgehrke
Copy link
Member

georgehrke commented Aug 18, 2018 •
edited
Loading

Don't query everything all over and all over again, sync changes instead

https://tools.ietf.org/html/rfc6578
@georgehrke georgehrke added the enhancement New feature or request label Aug 18, 2018
@georgehrke georgehrke added this to the 0.0.3 milestone Aug 18, 2018
@georgehrke georgehrke added feature: CalDAV Related to CalDAV feature: CardDAV Related to CardDAV labels Aug 18, 2018
@georgehrke georgehrke mentioned this issue Nov 21, 2018
Merged
30 tasks
@georgehrke georgehrke removed this from the 0.0.3 milestone Jan 31, 2020
@azul azul mentioned this issue Feb 23, 2021
Closed
2 tasks
azul added a commit to nextcloud/calendar that referenced this issue Feb 25, 2021
@azul
Check for updates and update public calendars
23e80a0 
Fetch the open calendars every 20 seconds
and check if they have changed since they were loaded.

If a calendar changed remove all it's data from the store
and thereby effectively trigger a reload.

This is a fairly brute force approach as it drops all known data
rather than fetching only the data that changed via the caldav sync API.

However Caldav sync is yet to be implemented. (nextcloud/cdav-library#9)
So this serves as a workaround for the time being.
azul added a commit to nextcloud/calendar that referenced this issue Feb 25, 2021
@azul
Check for updates and update public calendars
2e4a9d0 
Fetch the open calendars every 20 seconds
and check if they have changed since they were loaded.

If a calendar changed remove all it's data from the store
and thereby effectively trigger a reload.

This is a fairly brute force approach as it drops all known data
rather than fetching only the data that changed via the caldav sync API.

However Caldav sync is yet to be implemented. (nextcloud/cdav-library#9)
So this serves as a workaround for the time being.

See #31.
azul added a commit to nextcloud/calendar that referenced this issue Feb 25, 2021
@azul
Check for updates and update public calendars
cfab71b 
Fetch the open calendars every 20 seconds
and check if they have changed since they were loaded.

If a calendar changed remove all it's data from the store
and thereby effectively trigger a reload.

This is a fairly brute force approach as it drops all known data
rather than fetching only the data that changed via the caldav sync API.

However Caldav sync is yet to be implemented. (nextcloud/cdav-library#9)
So this serves as a workaround for the time being.

See #31.

Signed-off-by: Azul <azul@riseup.net>
@azul azul mentioned this issue Feb 25, 2021
Open
13 tasks
azul added a commit to nextcloud/calendar that referenced this issue Feb 26, 2021
@azul
Check for updates and update public calendars
a8a5112 
Fetch the open calendars every 20 seconds
and check if they have changed since they were loaded.

If a calendar changed remove all it's data from the store
and thereby effectively trigger a reload.

This is a fairly brute force approach as it drops all known data
rather than fetching only the data that changed via the caldav sync API.

However Caldav sync is yet to be implemented. (nextcloud/cdav-library#9)
So this serves as a workaround for the time being.

See #31.

Signed-off-by: Azul <azul@riseup.net>
azul added a commit to nextcloud/calendar that referenced this issue Feb 26, 2021
@azul
Check for updates and update public calendars
f52f6e5 
Fetch the open calendars every 20 seconds
and check if they have changed since they were loaded.

If a calendar changed remove all it's data from the store
and thereby effectively trigger a reload.

This is a fairly brute force approach as it drops all known data
rather than fetching only the data that changed via the caldav sync API.

However Caldav sync is yet to be implemented. (nextcloud/cdav-library#9)
So this serves as a workaround for the time being.

See #31.

Signed-off-by: Azul <azul@riseup.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request feature: CalDAV Related to CalDAV feature: CardDAV Related to CardDAV
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@georgehrke