Status

RESOLVED WONTFIX
10 years ago
4 years ago

People

(Reporter: WSourdeau, Unassigned)

Tracking

Details

(Whiteboard: [calconnect31])

(Reporter)

Description

10 years ago
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
(Reporter)

Comment 1

10 years ago
"This void..." -> "This WOULD..."
Whats the worst thing that could happen here? Additional network requests after adding items?
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Reporter)

Comment 3

9 years ago
(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.
Whiteboard: [calconnect31]
I think we can live with the extra network requests, especially given webdav-sync is the future.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.