[jira] Created: (DIRSTUDIO-303) Abstract connection concept to allow pseudo connections to ApacheDS partitions

["Alex Karasulu (JIRA)" <ji...@apache.org>]

Abstract connection concept to allow pseudo connections to ApacheDS partitions
------------------------------------------------------------------------------

                 Key: DIRSTUDIO-303
                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-303
             Project: Directory Studio
          Issue Type: New Feature
         Environment: all platforms
            Reporter: Alex Karasulu
            Priority: Minor


It would be neat if we could abstract connections enough so local Apache DS partitions loaded by Studio can be presented as connections for the sake of super fast import export operations against them.  This would be analogous to using slapxxx operations with like OpenLDAP and other umich based servers.  These operations are extremely fast since they do not have to go through the protocol and through interceptors.  They may cut down maintenance operations against the Directory Information Base (DIB) by one or two orders of magnitude.  For VLDB this will be very valuable.

Some comments.  We're already familiar with the connection wizard today for remote connections.  This wizard can be enhanced to ask which kind of connections the user wants.  For example we can have the following connection type options:

(1) Remote LDAP Server
(2) Local Partition/Backend

In the future you can have different "personalities" for these kinds of connections for the various kinds of servers and backends.  No need to limit this to only Apache DS partitions, it could work for OpenLDAP backends as well.

So if the user selects the second option, then you might show a selector for the kind of "personality" a.k.a. ApacheDS-JDBM, or OpenLDAP-BDB etc.  After this is selected, and based on the selection reflexively a different dialog would appear to collect "personality" specific information such as an installation file path, and perhaps some optional cache parameters who knows.

Another optional approach might be to point studio to a server's installation path or it's configuration file, and then just like the standard wizard for selecting namingContexts for the connection, have the dialog list the namingContext (corresponding to partitions) then the partition can be selected and it's personality would be known from the configuration of the server.  Users can select that partition and wa'la they have the connection object.

This way by abstracting connection objects, the full capability of the browser, LDIF importer and exporter is available for against local installations at lightning fast speeds.



 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.