All users were logged out of Bugzilla on October 13th, 2018
This bug is to implement offline support by having a local changelog, and play that changelog when coming back online. Filed as a separate bug, to not make a generic offline support bug unreadable when this attempt fails.
Created attachment 251387 [details] [diff] [review] work in progress Attached file is very much work in progress. It's a xpcshell script that implements the changelog part. Now we just need the offline part...
Assignee: nobody → mvl
Status: NEW → ASSIGNED
Created attachment 259020 [details] work in progress Attached a newer version of the script. Still only proof-of-concept. To be used in xpcshell.
Attachment #251387 - Attachment is obsolete: true
hi, This is (I think) exactly what I am looking for, hence I am adding my use case here. I hope this helps and is not a breach of mozilla etiquette! =============================================== My use case: 1) work computer 2) laptop 3) home computer all three with Sunbird installed. I want to have them all agree on what I am supposed to be doing. Hence the calendar is stored on a webdav store, all three machines point to this webdav store. If I add an event at home in the evening, the event is seen at work in the morning. Sometimes I am in a hotel room with my laptop. I don't have internet connectivity at that moment. This is my use case for "support for offline remote calendar" : a) I want to be able to see my calendar, even though I am not on the network. hence there needs to be some type of local (ie actually on the hard disk of the laptop) calendar storge b) I want to be able to add a new event while in disconnected mode; whenever I connected back to the network, this new event should be propagated back to the webdav store. Note : I do *not* have a use case for simultaneous edits. Only one machine will be editing the calendar at any one time.
Re-assigning to nobody.m.o. Mvl, if you still work on this feature, just re-assign the bug to yourself.
Assignee: mvl → nobody
Status: ASSIGNED → NEW
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 380060
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.