[ 
http://issues.apache.org/jira/browse/FTPSERVER-19?page=comments#action_12331263 
] 

Sergey Vladimirov commented on FTPSERVER-19:
--------------------------------------------

Hmm... after trying to implement, some features are showed:

 - not only canSomething(), but also getFullName(), delete(), mkdir(), etc 
moved to FileSystemView. All methods of FileObject not throws exception, but 
methods of FileSystemView of FileSystemManager throw.
 - there is only one full name - full name for user, getted from 
fileSystemView.getFullName(). But file must contains SystemID() to allow 
caching of FileObject at FileSystemManager level.

And about cache: caching is optional feature. Simple managers, like virtual or 
native file managers doesn't need them, in most cases.

There is also should be abstract classes, like AbstractFileManager and 
AbstractFileView, to simplify developing them.

I'm working on it.

> Question about FileObject - should it depends on User?
> ------------------------------------------------------
>
>          Key: FTPSERVER-19
>          URL: http://issues.apache.org/jira/browse/FTPSERVER-19
>      Project: FtpServer
>         Type: Wish
>     Reporter: Sergey Vladimirov

>
> Does FileObject need to depend from User, or different users can share same 
> FileObject?
> Second variant is good choice for caching and reusing file objects - we can 
> put all files to cache (where key is they full name), and user-depended code 
> will be only in FileSystemView.
> Now first variant is implemented.
> If no marks or suggestions until Tuesday evening (MSK), I will do it - it the 
> simpliest way to implement files security chinking in my system (Arp.Site).
> (Please, report me, if you found a bug in my English :) Patches are welcome )

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to