[Kroupware] Kolab IMAP -> iCal

[Diego Rivera]

On Fri, 2003-05-30 at 15:28, Jason A. Pattie wrote:
> Conclusion:
> The privileged user approach is more efficient and better if it can be
> done securely.

I'm glad you agree that the "privileged user" approach for imap->ical
fits best.

Legacy mode (which is what this really is, parts of it at least) is not
required to be secure in the first place.  At least that's what the
architecture docs say.  I agree that https should be used where
possible, though.  That's why I like this approach - it fits with the
existing architecture and design thinking.

Future enhancements could allow a user to have multiple DIFFERENT
calendar folders, and publish their free/busy information for all, some
or none of them, where overlapping entries between calendars are
consolidated and published as one big "busy" or "free" block.

As for ical->imap, that's another issue, and as I've said before, I have
no say in the matter at this time.  :)

Best

-- 
===========================================================
* Diego Rivera                                            *
*                                                         *
* "The Disease: Windows, the cure: Linux"                 *
*                                                         *
* E-mail: lrivera<AT>racsa<DOT>co<DOT>cr                  *
* Replace: <AT>='@', <DOT>='.'                            *
*                                                         *
* GPG: BE59 5469 C696 C80D FF5C  5926 0B36 F8FF DA98 62AD *
* GPG Public Key avaliable at: http://pgp.mit.edu         *
===========================================================
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://mail.kde.org/pipermail/kroupware/attachments/20030530/756445a2/attachment.bin