We should have done this from day one. I had warned about using serialized objects but the original implementor did not seem to listen.  Mitosis needs a clean redesign.

I'd like to see the following things happen:

(1) Move the UUID generation go into the OperationAttributeInterceptor removing it from mitosis so UUIDs are there regardless of replication.

(2) Remove the dependency on Derby and use a custom replication store.  I don't think we need the replication store if we do #3 below.

(3) Remove this hack with tombstone entries.  Instead we can rely on the changelog to revert deleted entries.  Mitosis should enable the changelog if it is started.

(4) Solid configuration via subentries.  I'd like to use the administrative model to configure replication instead of the crap we have today.

(5) Fractional and partial replication is needed.

(6) Different modes of operation so it can interoperate with OpenLDAP (heterogenous mix of OLD and ADS in a cluster)


On Mon, Aug 11, 2008 at 8:03 AM, Emmanuel Lecharny (JIRA) <jira@apache.org> wrote:
Replication should transfer textual objects

                Key: DIRSERVER-1227
                URL: https://issues.apache.org/jira/browse/DIRSERVER-1227
            Project: Directory ApacheDS
         Issue Type: Improvement
           Reporter: Emmanuel Lecharny
            Fix For: 2.0.0

When replication is running, some entries and modification are transmitted to the replicas. Atm, we are transmitting serialized version of JNDI attributes and modification.

It would be much better to transfer either LDIF or DSML elements, so that we can interrop with some other LDAP servers (see https://opends.dev.java.net/public/standards/draft-chu-ldap-logschema.txt for a data format)

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

Microsoft gives you Windows, Linux gives you the whole house ...