You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Olivier Lourdais (JIRA)" <ji...@apache.org> on 2008/08/06 17:28:44 UTC

[jira] Created: (FTPSERVER-146) Volatile user manager

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
            Priority: Minor


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.

[jira] Updated: (FTPSERVER-146) Volatile user manager

Posted by "Niklas Gustavsson (JIRA)" <ji...@apache.org>.
     [ 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.

[jira] Commented: (FTPSERVER-146) Volatile user manager

Posted by "Niklas Gustavsson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FTPSERVER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620291#action_12620291 ] 

Niklas Gustavsson commented on FTPSERVER-146:
---------------------------------------------

I think having an in-memory user manager makes total sense. As we're planing to replace PropertiesUserManager with the JSecurity PropertiesRealm for M3, I think making any major changes to PropertiesUserManager makes less sense now. I do think we should do an in-memory realm for JSecurity. 

Would you be able wait for such a change? 

> 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
>            Priority: Minor
>
> 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.

[jira] Closed: (FTPSERVER-146) Volatile user manager

Posted by "Niklas Gustavsson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FTPSERVER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Niklas Gustavsson closed FTPSERVER-146.
---------------------------------------

    Resolution: Fixed

Fixed in rev 711965. Set the file to null and it will be volatile.

> 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.

[jira] Commented: (FTPSERVER-146) Volatile user manager

Posted by "Olivier Lourdais (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FTPSERVER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620294#action_12620294 ] 

Olivier Lourdais commented on FTPSERVER-146:
--------------------------------------------

Yes, there is absolutely no emergency for me.

> 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
>            Priority: Minor
>
> 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.