On Tue, 26 Sep 2006, Stephen McConnell <[EMAIL PROTECTED]> wrote:
> As such, some resource are implicitly file based (e.g. FileResource)
> while other resources may (or may not) be resolvable to a local
> file.
What kind of resources would that be?
> The important distinction here is that Path should allow any type of
> resource that is resolvable to a local file (but which is not
> necessarily a file resource).
I agree under the assumption that such resources exist.
> However - there is nothing in the definition of Resource that allows
> an implementation to return a local file. Instead the current model
> assumes that only FileResource is a valid source of a local file.
Or the recommended extension point for custom resources that are
resolvable to local files.
> This could be resolved by separating the concern of local file
> resolvability via a interface dedicated to this concern .. E.g.
>
> public interface LocalFileProvider
> {
> File getFile();
> }
Would work and it would even be pretty easy to retrofit the
implementation of isFilesystemOnly to look after that interface
instead of the FileResource class. Same for task that only work on
FileResources right now.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
