Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: domain of mario@ops.co.at designates
 194.152.182.4 as permitted sender)
Message-ID: <42A04771.5040104@ops.co.at>
Date: Fri, 03 Jun 2005 14:05:05 +0200
From: Mario Ivankovits <mario@ops.co.at>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041207)
MIME-Version: 1.0
To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
Subject: Re: [VFS]  VFS.getManager().getFilesCache() - exists() vs findFiles()
References: <20050518225313.30303.qmail@web31512.mail.mud.yahoo.com>
 <428C2457.9090504@ops.co.at> <428C8D71.3080008@ascii27.net>
 <428CC1C4.80206@ops.co.at> <429DE963.1050706@sophia.inria.fr>
 <429DF548.8040706@ops.co.at> <429ED24B.4050800@sophia.inria.fr>
 <429EE996.5070409@ops.co.at> <429F1F2D.1040504@sophia.inria.fr>
 <42A00594.3080505@ops.co.at> <42A03C76.9070806@sophia.inria.fr>
In-Reply-To: <42A03C76.9070806@sophia.inria.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Philippe Poulard wrote:
> these attributes are tightly coupled to this scheme
> so if you have "xmldb:provider://..." somewhere, you also have 
> attribute settings beside
> thus, when you make the switch from xmldb to -say- ftp, this includes 
> to clean attributes becoming irrelevant
Is it possible to separate those attributes into
* filesystem attributes
* file attributes
?

I ask as e.g. the "cluster" sounds more like a configuration per 
filesystem instance.
VFS currently supports such filesystem attributes and one thing we can 
do here is to register a virtual scheme to a set of filesystem attributes:
say:
xmldbRaweb2004:xyl://user:pwd@www.foo.com/path/to/file.xml

would point to the scheme "xmldb" with the desired filesystem attributes 
attached.


For the "file attributes" I will take some time to think about them.
What if we create a new method "FileObject.createFile(Map attributes)"?
That way there is no need to change the contract of the IMAGINARY file 
type and it makes clear that if you would like to create a new file with 
special attributes you have to call that method.

Ciao,
Mario


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