On Mon, Dec 10, 2001, Peter C. Norton <spac...@lenin.nu> wrote:
Is there any intention to make the calendar backend work as an icalendar
(rfc 2445). I'm starting to read the rfc, and I've noticed that there's the
beginnings of an implementation of some part of the library under the name
of libical at sourceforge.
Again, focusing on evolution (and I guess outlook and netscape) having a
calendar server as part of courier would be cool. I'm going to assume,
before reading the RFC, that implementing an icalendar server is a PITA, but
if it is possible has anyone done it, and would having courier's calendar
access this be useful?
I brought this up when Sam released his first code. At the time, he
showed little interest.
As far as iCalendar goes, it's merely a feature set and higher level
protocol to exchange calendar information between clients.
It doesn't define an on disk storage format and there is no standard for
a client/server setup either.
The little that I looked at the calendar code in courier made it look
like it's a subset of the iCalendar feature set.
I think we could implement a libical backend for the storage format Sam
developed which would cover the higher level protocol atleast.
JE
3 messages in net.sourceforge.lists.courier-usersRe: [courier-users] calendar goals?
