Closed
Bug 400283
Opened 17 years ago
Closed 16 years ago
CalDAV provider issues too many requests
Categories
(Calendar :: Provider: CalDAV, defect)
Calendar
Provider: CalDAV
Tracking
(Not tracked)
RESOLVED
FIXED
0.8
People
(Reporter: nomisvai, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.8pre) Gecko/20071016 Sunbird/0.7 The CalDAV provider issues too many requests, for example: At startup: - PROPFIND (to get resourcetype) - 5 VTODO reports - 6 VEVENT reports When doing next month: - 2 VTODO reports - 2 VEVENT reports For performance reasons, these 2 sequences should be done as 1 VEVENT report and 1 VTODO report. (Also you might end up with weird scenarios if an event or task is deleted/added by another party between 2 requests, the object will be displayed in one view and not the other..). This has a significant impact on performance when using a calendar with many calendar objects. Reproducible: Always Steps to Reproduce: 1.Start sunbird 2.Move from month to month 3. Actual Results: Lots of redundant requests are sent to the server. Expected Results: One request for VTODO and one request for VEVENT. The provider should then filter the results for each views in Sunbird.
Comment 1•17 years ago
|
||
This will clear up as soon as offline support or at least calendar caching is implemented. Currently a getItems call is issued by each part of the program (i.e views, unifinder, ...). If this is cached, then only one getItems call will be passed on to the provider and the rest will be retrieved from the local cache.
Reporter | ||
Comment 2•16 years ago
|
||
bug 393817 seems to have greatly improved this issue, I think this bug should be closed.
Comment 3•16 years ago
|
||
based on comment #2 ->FIXED
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
OS: Windows XP → All
Hardware: PC → All
Target Milestone: --- → 0.8
You need to log in
before you can comment on or make changes to this bug.
Description
•