Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
From: Adam Murdoch <adammurdoch@apache.org>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: VFS and JNDI
Date: Wed, 26 Feb 2003 13:27:09 +0000
User-Agent: KMail/1.5
References: <3E5C23C4.8040501@hanaden.com>
In-Reply-To: <3E5C23C4.8040501@hanaden.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200302261327.09890.adammurdoch@apache.org>

On Wed, 26 Feb 2003 02:17 am, Hanasaki JiJi wrote:
> Any comparisons on VFS vs JNDI?  seems very similar to me.

They are very similar.  JNDI is a little more general: a namespace of Objects.  
VFS is a little more specific: a hierarchy of files.

VFS does not try to be as universal as JNDI does, even though there is going 
to be plenty of overlap (find by name, create, delete, get/set attribute, 
etc).  VFS adds things that don't make sense under JNDI's more general model 
(get content as a stream, content signing, copy a tree, converting to/from 
java.io.File, etc), and does things in a way that reflects how files get used 
(as opposed to how generic namespaces of Objects get used).

-- 
Adam

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org