[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Inf-IT DAVcl] InfCloud is failing on me...
- Subject: Re: [Inf-IT DAVcl] InfCloud is failing on me...
- From: Ján Máté <jan.mate@xxxxxxxxxx>
- Reply-to: davclients@xxxxxxxxxx
- Date: Wed, 7 Mar 2018 19:26:37 +0100
- To: davclients@xxxxxxxxxx
Hi Johan, it may or may not be an InfCloud bug ... and here is why; there are 2 types of clients: - clients which use PROPFIND requests to the list of ALL available objects on the server and then MULTIGET request (with a list of URLs from the previous step) to get the "raw" data from the server ... advantages: you always get ALL objects back from the server (trivial server implementation) disadvantages: it can be EXTREMELY slow, because the PROPFIND request always lists all the objects on the server, and then the client needs to find the "diff" between the previous list of objects and the current list of objects (using Etags) and then provide the MULTIGET request to download only the new/changed objects - clients which use: a.) REPORT request to get the list of CHANGED objects from the server (using sync-token) and then use MULTIGET to get the "raw" data from the server advantages: very fast on client side and may be very fast on server side too (if implemented properly) disadvantages: if implemented improperly then some changes may not sync => possible problem #1 b.) time-rage filtering to get only subset of objects from the server (e.g. for the current view) advantages: you get only the data for the current view and not the whole list of events from -infinity to +infinity (fast for clients and servers too) disadvantages: especially for repeating events the server needs to "expand" the events to all "instances", and then provide the time-range filtering on these instances (not on the stored object itself) ... if the event is not "expanded" as it should, then it is NOT returned back to the client => possible problem #2 So what you must check is the list of requests and responses from the server, more precisely whether your repeating events are returned from the server or not - if yes, it can be InfCloud (or rrule.js) problem; if not then it is a server problem Cheers, JM p.s.: cache_update cannot solve this problem, it only forces your browser to download the InfCloud source code again ... > On 7 Mar 2018, at 18:56, Johan Vromans <jvromans@xxxxxxxxxxx> wrote: > > All of a sudden InfCloud is missing events. > > I'm running InfCloud 0.13.2.rc2 since the end of 2015 using FireFox on > Fedora. The DAViCal server is running on a separate system. > > InfCloud didn't change and neither did the DAViCal server. I did upgrade > FireFox as part of regular system upgrades. > > This morning I noticed, the hard way, that a repeating event was missing > from InfCloud. It is just gone. All occurrences, including past occurrences. > > The event is on the server, since other clients (Android phones and > tablets) display it. > > This worries me very much. Is there anything I can do to find out what is > going on? I tried cahce_update but that didn't make a difference. > > Update: InfCloud with Chromium doesn't show the missing events either. >
Description: S/MIME cryptographic signature
|Re: [Inf-IT DAVcl] InfCloud is failing on me...||Johan Vromans <jvromans@xxxxxxxxxxx>|
|[Inf-IT DAVcl] InfCloud is failing on me...||Johan Vromans <jvromans@xxxxxxxxxxx>|