[
https://issues.apache.org/jira/browse/FTPSERVER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson updated FTPSERVER-146:
----------------------------------------
Fix Version/s: 1.0-M4
Assignee: Niklas Gustavsson
> Volatile user manager
> ----------------------
>
> Key: FTPSERVER-146
> URL: https://issues.apache.org/jira/browse/FTPSERVER-146
> Project: FtpServer
> Issue Type: Improvement
> Components: Core
> Reporter: Olivier Lourdais
> Assignee: Niklas Gustavsson
> Priority: Minor
> Fix For: 1.0-M4
>
>
> Context: FTPSERVER-144
> We use Apache FTP Server embedded in an application (to allow some devices to
> download firmware updates).
> We would like this application let less files as possible on the user
> computer. Or at least, only files whose names are prefixed by the application
> name.
> Use an appropriate name for the users properties file is acceptable for me,
> but the best would be to have no file at all. Our application creates and
> destroys FTP users on the fly, and all users are always destroyed when the
> application exits. So we have no real need for such a file, and we would like
> to avoid writing it.
> A solution would be to split PropertiesUserManager onto 2 classes:
> - a super-class which owns the BaseProperties object, implements user
> management and authentication,
> - a sub-class which handles the storage of the properties file.
> Another solution would be to allow the userDataFile attribute of
> PropertiesUserManager to take null value, which would mean that storage is
> disabled.
> What is your opinion on that? I can send a patch but maybe you have some
> projects for this class...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
