[
https://issues.apache.org/jira/browse/DIRSTUDIO-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501480
]
Pierre-Arnaud Marcelot commented on DIRSTUDIO-123:
--------------------------------------------------
I think, it could be a good thing to build a separate plugin for the
connections handling.
This way, connections defined in this plugin can be shared by several plugins:
the LDAP Browser plugin of course, but the dynamic online schema editor plugin
also, etc.
Since you plan to refactor this class and interface, it could be the good
timing to build such a plugin.
> Refactor IConnection interface and Connection class
> ---------------------------------------------------
>
> Key: DIRSTUDIO-123
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-123
> Project: Directory Studio
> Issue Type: Improvement
> Components: ldapstudio-browser
> Affects Versions: 0.8.0
> Reporter: Stefan Seelmann
> Priority: Critical
>
> The IConnection interface and the Connection class (and its dependent
> classes) needs to be refactored:
> - They are just too big: The IConnection interface defines 65 methods, the
> Connection class has more than 1000 LOC and no line of Javadoc :-(
> - The procedure of opening a connection (connect, bind, load RootDSE,
> cache/refresh schema, load base entries) is just horrible
> - The Connection class uses LDIF as an interface between the browser classes
> and the JNDI layer to retrieve information from the directory or to commit
> modifications. This causes heavy CPU consumption and slows down mass
> operations.
> - In order to support new features lik strong authentication with SASL,
> extended operations and controls we also have to extend the IConnection
> interface.
> I will create an confluence page that shows the current design. It would be
> cool if we could discuss the needed requirements and improve the design.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
