Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 9994 invoked from network); 4 Jan 2004 18:06:02 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Jan 2004 18:06:02 -0000 Received: (qmail 23591 invoked by uid 500); 4 Jan 2004 18:05:53 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 23531 invoked by uid 500); 4 Jan 2004 18:05:53 -0000 Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Directory Developers List" Reply-To: "Apache Directory Developers List" Delivered-To: mailing list directory-dev@incubator.apache.org Received: (qmail 23467 invoked from network); 4 Jan 2004 18:05:52 -0000 Received: from unknown (HELO imf24aec.mail.bellsouth.net) (205.152.59.72) by daedalus.apache.org with SMTP; 4 Jan 2004 18:05:52 -0000 Received: from franklin ([66.157.215.32]) by imf24aec.mail.bellsouth.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040104180556.THBZ1911.imf24aec.mail.bellsouth.net@franklin> for ; Sun, 4 Jan 2004 13:05:56 -0500 From: "Alex Karasulu" To: "'Apache Directory Developers List'" Subject: RE: [JXPath] Plans for JNDI, JMX and Filesystems? Date: Sun, 4 Jan 2004 13:05:53 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcPS5cDF0BgEgOhjSwe47a2rywqyUAAAPnTwAAFQg1AAAEZpIA== In-Reply-To: <20040104175849.CFPY18876.imf13aec.mail.bellsouth.net@minotaur.apache.org> Message-Id: <20040104180556.THBZ1911.imf24aec.mail.bellsouth.net@franklin> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Mark, I don't think we will use WebDAV for Eve but there are other projects that will be part of the directory top level project. These projects include JNDI providers for various directories or naming systems. I have just always wanted to have a JNDI provider for WebDAV and don't necessarily intend to use if within Eve. Sorry for the confusion, Alex > -----Original Message----- > From: Mark Imel [mailto:mimel@imelshire.com] > Sent: Sunday, January 04, 2004 12:59 PM > To: 'Apache Directory Developers List' > Subject: RE: [JXPath] Plans for JNDI, JMX and Filesystems? > > I noticed webDav mentioned below and it caught my eye... > Out of curiosity, could you please elaborate on how webDav is going to be > used for Eve? > > I've written a couple of webDav 'lite' implementations in the past and I'd > like to see if this would be a way that I could contribute to your > project. > > -----Original Message----- > From: Alex Karasulu [mailto:aok123@bellsouth.net] > Sent: Sunday, January 04, 2004 9:22 AM > To: 'Apache Directory Developers List' > Subject: RE: [JXPath] Plans for JNDI, JMX and Filesystems? > > Phil, > > > -----Original Message----- > > From: Phil Steitz [mailto:phil@steitz.com] > > Sent: Sunday, January 04, 2004 12:11 PM > > To: Apache Directory Developers List > > Subject: Re: [JXPath] Plans for JNDI, JMX and Filesystems? > > > > Alex Karasulu wrote: > > > > >> > > >>Yes, a fs context provider would make a good addition to directory- > > naming. > > > > > > > > > Here, here! I agree as well. Also on my wish list are the following > > > JNDI providers: > > > > > > Webdav/DeltaV > > > > Also partially there in the naming code. See DirContextURLConnection > > (uses Webdav attributes). > > > > Very cool - I'll try to take a look at it when I get a chance. Also I > agree > the NTFS notification stuff will not be easy and will require native code > unless the java.io.File construct supports hooks for it down the road but > I'm not going to hold my breath either. It would be nice to have though. > I > just hate having to poll for file changes due to other processes. > > Thanks, > Alex >