[
https://issues.apache.org/jira/browse/DIRSTUDIO-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seelmann updated DIRSTUDIO-123:
--------------------------------------
Fix Version/s: 1.1.0
Assignee: Stefan Seelmann
Affects Version/s: 0.8.1
0.8.2
1.0.0
> 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: studio-ldapbrowser
> Affects Versions: 0.8.0, 0.8.1, 0.8.2, 1.0.0
> Reporter: Stefan Seelmann
> Assignee: Stefan Seelmann
> Priority: Critical
> Fix For: 1.1.0
>
>
> 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.
