Hi all, I will move apacheds component/feature from carbon core to components. This way we can avoid embeded ldap server within all products and add the feature only to identity server.
If you have no concern on this, I will move on. Thank you. On Tue, Jun 28, 2011 at 11:57 AM, Amila Jayasekara <[email protected]> wrote: > Hi All, > > It seems that lot of members were under the impression that embedded > LDAP server is not binding an address. Thus most of the people are > under the impression that it behaves like H2. But this is not the > case. > > We (me, Shankar, Amila and Azeez) had a discussion about this. > As per our current implementation we have LDAP servers embedded in all > products. Also it seems having LDAP servers in all products is not > architecturally sound. > > Thus apacheds has a way of by passing the network layer and using just > like H2. For this we need to write a new user store manager. But IMO > we are not going to gain much from implementing a user store manager > which uses only apacheds (By passing network layer). Instead we could > use H2. > > So the conclusion was to use apacheds only within Identity Server and > make it an optional feature for other products. Other products will > use H2 as it was used to be. > > Please let us know what you all think about this conclusion. > > Feedback appreciated. > > Thanks > AmilaJ > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
