Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Received-SPF: pass (hermes.apache.org: domain of bcm@osafoundation.org
 designates 204.152.186.98 as permitted sender)
Message-ID: <4239E652.5040004@osafoundation.org>
Date: Thu, 17 Mar 2005 12:19:30 -0800
From: Brian Moseley <bcm@osafoundation.org>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
MIME-Version: 1.0
To: jackrabbit-dev@incubator.apache.org
Subject: Re: WebDAV/CalDAV and remote content stores
References: <422DECFF.5080503@osafoundation.org>
	 <e84ee3db586c8f9c545502887b508520@gbiv.com>	 <422E7768.2000102@apache.org>
 <422E8958.8010408@osafoundation.org>
	 <eb7e2190503091426498d3cb9@mail.gmail.com>
	 <42307479.5010301@osafoundation.org>
 <eb7e21905031614543e1c8a7c@mail.gmail.com>
In-Reply-To: <eb7e21905031614543e1c8a7c@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

David Nuescheler wrote:

> well, actually i would not store the iCalendar body as a data property,
> but "simulate" an iCalendar file serialization in the webdav layer.
> once somebody PUTs any iCalendar file i would automatically 
> deserialize it into the iCalendar properties.
> does that make sense?

yep, it does. that strategy will support CalDAV iff the properties can 
reliably be reconstituted into the exact same iCalendar body every time 
it is requested.

> cool, do you have already have an idea about the 
> structure of the iCalendar nodetype(s)?

not yet - i'm still working on integrating Jackrabbit and jcr-server 
with a security framework (Acegi Security) and establishing a web ui for 
managing users and access control. when that's working, i'll be ready to 
start looking at what needs to be done for CalDAV support.