--- "Alexey N. Solofnenko" <[EMAIL PROTECTED]>
wrote:
> Can it be - copy+delete in that case?
Okay... here's what I did for preserving timestamps in
FileUtils copy methods. I added a Touchable interface
to the resources package. FileResource is (so far)
the only Resource that uses it, but I was thinking
along the lines of FTP/SCP Resources when I added it.
So by that token, you would similarly add a Deletable
(?) interface for FileResource to implement. So then
move could fail when encountering a Resource that does
not implement Deletable... that is the only sensible
way that occurs to me to support Resource deletion.
-Matt
>
> - Alexey.
>
> Matt Benson wrote:
>
> >... Regarding the Move task, I don't see that we
> could
> >move non-file resources in a predictable way so I
> >would recommend failing on ResourceCollections that
> do
> >not return true from isFilesystemOnly().
> >
> >Thoughts?
> >
> >-Matt
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new Resources site
http://smallbusiness.yahoo.com/resources/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
