[Kolab-devel] shared calendar as long time reminding system?

Bernhard Reiter bernhard at intevation.de
Mon Sep 14 11:59:59 CEST 2009


Am Freitag, 11. September 2009 16:13:45 schrieb Gunnar Wrobel:
> > I guess the hackish solution would be to make sure a webclient is running
> > all the time that has access to the folder and will just send out emails
> > for each reminder. You might need a script to keep the horde sessing
> > alive, though.
> >
> > A better solution would be to implement a daemon that does the same job.
> > It would be less code, more robust, secure and flexible.
> >
> > An even better, but more long time solution would be to enhance Kolab
> > Storage format and add a standard daemon for such purposes or come up
> > with something else that does time based events.
>
> I think it would also be possible to extend the Kolab Free/Busy system  
> to keep track of reminders. Or to use something similar that allows  
> triggering. We'd only export data relevant for the reminder on  
> triggering and thus wouldn't compromise security of the imap system.

This is one possible design. I wonder thought if we would want to have 
feedback on who got reminded when, just triggering would be enought.
Also the contents of the reminder might be worth being protected.
Still we would need a daemon to check for the reminders.

Bernhard


-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20090914/c2ac84ba/attachment.sig>


More information about the devel mailing list