Confirmed users
503
edits
User:Mvl/sharing: Difference between revisions
Jump to navigation
Jump to search
→Technical Implementation
No edit summary |
|||
| Line 15: | Line 15: | ||
The changelog could be created using x-properties inside the events. The events will also need a version counter. | The changelog could be created using x-properties inside the events. The events will also need a version counter. | ||
It would make sense to base the implementation on the ics provider. The problem with that would be to add the custom properties (to indicate changes) to the events. | It would make sense to base the implementation on the ics provider. The problem with that would be to add the custom properties (to indicate changes) to the events: The ics provider manages the uploading of the file. Any wrappers of observers might not be able to add properties to events before the calendar is uploaded (depending on the order in wich the observer and the uploader are called). | ||
A more advanced solution could be to use the storage calendar as backend (for speed). Then, using an observer, whenever something changes a new ics file can be published, including properties that indicate changes. | A more advanced solution could be to use the storage calendar as backend (for speed). Then, using an observer, whenever something changes a new ics file can be published, including properties that indicate changes. | ||