You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Miroslav Pokorny (JIRA)" <ji...@apache.org> on 2011/07/19 11:39:59 UTC
[jira] [Created] (VFS-357) FtpFileSystemConfigBuilder and other
builders are all singletons which leads to problems if one wishes ftp
connections with different incompatible settings.
FtpFileSystemConfigBuilder and other builders are all singletons which leads to problems if one wishes ftp connections with different incompatible settings.
------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: VFS-357
URL: https://issues.apache.org/jira/browse/VFS-357
Project: Commons VFS
Issue Type: Bug
Affects Versions: 1.0
Reporter: Miroslav Pokorny
RamFileSystemConfigBuilder also exhibits the same problem. The documentation does not make it sure if the max size is read during the factory or while running...
I believe it would be simpler to remove the singletonness and allow different objects to be created and set with their own properties.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (VFS-357) FtpFileSystemConfigBuilder and other
builders are all singletons which leads to problems if one wishes ftp
connections with different incompatible settings.
Posted by "Miroslav Pokorny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VFS-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067595#comment-13067595 ]
Miroslav Pokorny commented on VFS-357:
--------------------------------------
Im sorry my original statement was wrong, either way it would lead to less confusion (at least for me) if the builder wasnt a singleton or the doco stated it doenst contain state.
> FtpFileSystemConfigBuilder and other builders are all singletons which leads to problems if one wishes ftp connections with different incompatible settings.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: VFS-357
> URL: https://issues.apache.org/jira/browse/VFS-357
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Miroslav Pokorny
>
> RamFileSystemConfigBuilder also exhibits the same problem. The documentation does not make it sure if the max size is read during the factory or while running...
> I believe it would be simpler to remove the singletonness and allow different objects to be created and set with their own properties.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (VFS-357) FtpFileSystemConfigBuilder and other
builders are all singletons which leads to problems if one wishes ftp
connections with different incompatible settings.
Posted by "Ralph Goers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VFS-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved VFS-357.
-----------------------------
Resolution: Won't Fix
While I agree with this - I actually looked into providing an alternative to the ConfigBuilders a while ago - it just isn't worth the trouble in the current code base. VFS 3.0 should be based on Java 7 which should help clean this up.
> FtpFileSystemConfigBuilder and other builders are all singletons which leads to problems if one wishes ftp connections with different incompatible settings.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: VFS-357
> URL: https://issues.apache.org/jira/browse/VFS-357
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Miroslav Pokorny
>
> RamFileSystemConfigBuilder also exhibits the same problem. The documentation does not make it sure if the max size is read during the factory or while running...
> I believe it would be simpler to remove the singletonness and allow different objects to be created and set with their own properties.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira