[Kolab-devel] [issue2622] usability problem with cached freebusy lists: Very old ones might be shown without network.

[Bernhard Reiter]

New submission from Bernhard Reiter <bernhard at intevation.de>:

During freebusy tests for Prokde35 I found that there is a problem    
with freebusy list caching on the client.    
    
When requesting a freebusy list the first time, Kontact caches it    
in the directory .kde/share/apps/korganizer/freebusy/    
    
When there is no network connection and an ifb if requested,    
it will fall back on the cached files silently, potentially displaying    
very old and outdated information.    
It is useful to display cached ifb information, because old information    
might be better than no information, but very old information can be a problem.    
a) Thus I suggest to indicate the age of the used ifb information     
in the interface towards the user, at least in the case when it is not    
fetched from the server. So the user can decide.   
    
There are other minor quirks with the current implementation:    
b) Old ifb never get deleted, so you accumulate very old information in there.  
Better would be a cleanup after a while.  
c)  
Attention testers: Even when selecting: "Work offline" kontact still tries 
to fetch a fresh freebusy list.  
 
d) In case I get an authorisation dialog to enter the password for receiving 
the ifb list, there is already something displayed in the dialog.

----------
assignedto: till
messages: 14439
nosy: bernhard, ludwig, till, vkrause
priority: bug
status: unread
title: usability problem with cached freebusy lists: Very old ones might be shown without network.
topic: freebusy, kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue2622>
___________________________________________________