Thinking out loud here.... What do you think? 1. turn the VFS providers into JNDI SPI 2. implement VFS via JNDI or the JNDI SPI's directly
Adam Murdoch wrote:
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).
-- ================================================================= = Management is doing things right; leadership is doing the = = right things. - Peter Drucker = =_______________________________________________________________= = http://www.sun.com/service/sunps/jdc/javacenter.pdf = = www.sun.com | www.javasoft.com | http://wwws.sun.com/sunone = =================================================================
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
