498731 - ctag outdated after PUT

Status: RESOLVED WONTFIX

(Calendar :: Provider: CalDAV, defect)

Description

[Wolfgang Sourdeau]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9.0.10) Gecko/2009042805 Iceweasel/3.0.9 (Debian-3.0.9-1)
Build Identifier: 20090608035852

When creating an event, the ctag of the calendar collection will change but Lightning doesn't fetch it, which triggers a refresh of all the etags during the next refresh even though only one event has changed.

The most "secure" option would probably to fetch the ctag BEFORE the put and re-fetch it only if it the first fetch was different from the value stored in the calendar memory. This void avoid outside changes from being ignored during a further refresh.

Reproducible: Always

Comment 1

[Wolfgang Sourdeau]

"This void..." -> "This WOULD..."

Comment 2

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

Whats the worst thing that could happen here? Additional network requests after adding items?

Comment 3

[Wolfgang Sourdeau]

(In reply to comment #2)
> Whats the worst thing that could happen here? Additional network requests after
> adding items?

Yes. Note that the importance of that "bug" for us was solved by using webdav-sync.

Comment 4

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

I think we can live with the extra network requests, especially given webdav-sync is the future.