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 david.nuescheler@gmail.com
 designates 64.233.170.207 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=ePGXUyBZQi2wFCaG3bWMUWt9j/HMuqdIS/0+JlMe+1JZDikhjUdSvl3+k3Z6DuOgm9wdnA1OtFEYp76GDfBEh+jtZnijZ/bomNTWY57TKEgZgHnmTD8Vi8PJzC1TWLM9I/7XfLjvXp2CzuI7zS1j8hos3fMrq233ml+/xWji+Yg=
Message-ID: <eb7e21904103114485f486bd5@mail.gmail.com>
Date: Sun, 31 Oct 2004 23:48:50 +0100
From: David Nuescheler <david.nuescheler@gmail.com>
Reply-To: david.nuescheler@day.com
To: jackrabbit-dev@incubator.apache.org, ozeigermann@apache.org
Subject: Re: Adding WebDAV to Jackrabbit
In-Reply-To: <9da4f45204103114265c5a8682@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <9da4f45204103114265c5a8682@mail.gmail.com>

hi oliver,

thanks for your questions, let me just quickly comment:
> I had a look at the API and was wondering if there is anything
> concerning user and an advanced access rights management.
in jsr-170 all the administrational functions in a repository are
outside the scope of the spec (meaning that it is up to the
repository implementation to do that). 

> How would authentication work? 
the jsr-170 spec leaves it open how the authentication 
works however specifically mentions jaas. which probably
means since jackrabbit should also serve as an ri that we 
probably would at least implement jaas both for 
authentication and authorization. 
 
> How do you grant access rights?
as mentioned above the spec doesn't say anything about
that based on a concious decision to exclude it, since
repositories employ many different models of authorize. 

in jackrabbit i think we could start with a very straight 
forward acl based authorization model and in my mind 
user / group information should also be reflected in 
the repository. during the specification we thought
of a mixin nodetype called "accessControllable" which
would lead us to a very simple yet powerful 
implementation to get started.

> Is there anything like explicite locking of resources?
yes. in jsr-170 they are called nodes though ;)

> Can I make use of the transaction manager? Why haven 
> the JTA interfaces not been used?
yes, you can (should) use a transaction manager.
hmmm... are you looking beyond the XASession.getXAResource() ?

regards,
david
----------------------------------------------------------------------
standardize your content-repository !
                               http://www.jcp.org/en/jsr/detail?id=170
---------------------------------------< david.nuescheler@day.com >---

This message is a private communication. If you are not the intended
recipient, please do not read, copy, or use it, and do not disclose it
to others. Please notify the sender of the delivery error by replying
to this message, and then delete it from your system. Thank you.

The sender does not assume any liability for timely, trouble free,
complete, virus free, secure, error free or uninterrupted arrival of
this e-mail. For verification please request a hard copy version.


mailto:david.nuescheler@day.com
http://www.day.com

David Nuescheler
Chief Technology Officer
Day Software AG
Barfuesserplatz 6 / Postfach
4001 Basel
Switzerland

T  41 61 226 98 98
F  41 61 226 98 97