[kronolith] Calendar autorefresh

[Marcus]

Chuck Hagenbuch schrieb:
> Quoting Marcus <hordelist at quantentunnel.de>:
> 
>> I want the calender to autorefresh them self.
> 
> Why?


We use shared calendars in an office for appointments. Several people
are creating events with the workweek as default. When someone calls up
for an appointment none will think about refreshing the calendar.
Everyone is expecting to have the latest view. They are no experts, for
most of them Horde is just like any other program running on the desktop.

Events are created mostly by using new Event or the + Symbol before the
Day. I guess nobody will call the day view first, it's time you don't
have on a phone call.
Since the web browser is running the whole day with Kronolith, without
refreshing you'll get out of date pretty soon an

I just set refresh_time to 180 seconds, which is good enough. It's a LAN
Server and about 10 ppl. using it, so it won't hurt.

Of course i can see load problems for large user bases. But that's why
there should be a preference (default 0) where administrators can set
the time or even lock out the feature. This feature should only work for
shared calendars, it doesn't make sense for none shared calendars. So
maybe it's useful even in large installations when only a few calendars
with frequent changes are shared.

Just in case there still some worries, there are also extensions for
webbrowsers which can do refreshing of webpages. So ppl. can achieve
this /create load without the influence of an administrator.

IMHO showing an up to date view is a basic for calendars with different
clients. But maybe there is a better/faster way of achieving this with
some AJAX code. The webbrowser get's an notification from the server and
reloads the page, only if something changed in the current view.
This could reduce load, but on the other side all clients will update
their page at the same time. With the metatag "refresh", the page
reloads will spread over a wider time frame but even update if there is
no change.

Marcus