Re: [Evolution-hackers] calendar implementation (Partly OT)

["Ron Smits" <rons ronsmits com>]

But that is the whole point, I would not mind starting this project, but not
based on BEEP. CAP is theoretically sound ( I read the draft, this
afternoon) but indeed vaporware.

Smartest thing at this moment would be to use xml-rpc or http as protocol
engine.
I have even been thinking about just starting (My programming language
nowadays is java and I think Java would be very well suited for it. There
are already several good starts at ical objects.

Point here is that it will be to big for one person, design decisions will
have to be made and it would be nice if we could get some idea's support
whatever from ximian. I think it would be really good if we could make the
server in such a way that writing a backend for evo would be working fast

Ron

----- Original Message -----
From: "Dan Winship" <danw ximian com>
To: "stephen farrell" <sfarrell almaden ibm com>
Cc: "JP Rosevear" <jpr ximian com>; "Ron Smits" <rons ronsmits com>; "Helge
Hess" <helge hess skyrix com>; "Evolution hackers"
<evolution-hackers lists ximian com>
Sent: Thursday, April 10, 2003 6:35 PM
Subject: Re: [Evolution-hackers] calendar implementation (Partly OT)


> On Thu, 2003-04-10 at 12:12, stephen farrell wrote:
> > CAP is vaporware.
>
> I've been trying to believe this isn't true, but based on recent
> discussion on the ietf-calendar list, yeah, it's still going to be a
> while. :-/
>
> > Why not just enable the IMAP store to save calendar
> > events?
>
> As you noted, this has been discussed before, and there are technical
> arguments against it. But given the continued non-inevitability of CAP,
> there are arguments for it too. (The argument that it would be awkward
> to get it to work inside evolution's architecture still holds, but
> that's surmountable.)
>
> It's still not likely to end up on Ximian's to-do list at any point soon
> though. If people want to see it, they'll have to write the code
> themselves.
>
> -- Dan
>
>
>