[Ietf-caldav] CalDAV Client work?
lisa at osafoundation.org
Thu Aug 12 12:46:40 PDT 2004
The current plan for Chandler is to implement CalDAV, but not in the
0.4 release which is slated for Sept/Oct -- likely the 0.5 release but
who knows for sure. Things that will affect that schedule:
- will somebody else make available a CalDAV server in that time, for
us to test against
- will somebody else work on an open source CalDAV server
implementation, so we don't have to expend effort in that direction as
- normal vagaries of software development
Chandler also uses vanilla WebDAV to share its content items of all
types, and we'll have experimentally usable code that does that in 0.4.
We certainly intend to have short-lived connections where possible,
and to avoid the IMAP-style permanent-connection world where possible
(of course we have to do IMAP though). Since good offline
functionality is key to the Chandler vision, we definitely intend to
keep the client synchronized with the server as much as possible.
That's why features like SEARCH method aren't so important to the
single-user Chandler use cases -- we plan to have the user's own data
all synchronized locally, so why not do the search locally.
In the long run, we may look at things like how to make WebDAV
synchronization work better -- e.g. a feature track property changes,
as well as the existing HTTP ETag which tracks only entity (body)
changes. Also, how to make the non-persistent connection model still
appear responsive to users -- e.g. notifications through a notification
channel, to trigger a synch action, rather than constant polling.
On Aug 11, 2004, at 3:13 PM, Helge Hess wrote:
> anyone working on client software which implements CalDAV?
> Lisa, can we expect Chandler to implement CalDAV any time soon? I
> guess it would probably synchronize server data into its own
> repository instead of having a "live" connection?
> I think the OGo project would invest some work into adding CalDAV as a
> protocol. We already implement some parts of Exchange WebDAV protocol
> and patches for CalDAV shouldn't be too much work. Having some client
> vendor to work with would be of course great ;-)
> best regards,
> Ietf-caldav mailing list
> Ietf-caldav at osafoundation.org
More information about the Ietf-caldav