[Kroupware] Kolab IMAP -> iCal

[Jason A. Pattie]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Diego Rivera wrote:
> 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.

Only for public data.  For non-kroupware clients that need their private
data, obviously we want to authenticate the user against the Kolab server.

> 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.  :)

Hmm?  I thought that's what you said you were doing in a previous e-mail?

- --
Jason A. Pattie
pattieja at xperienceinc.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQE+1+IyuYsUrHkpYtARAvnuAJ49Zcq51NqBZnBgneDFUCKGK6wlJwCeO+Lz
toj8fJ+OsTe6HmUQDjSI1Fc=
=msJ8
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.