Hi guys,
those last days, we had to fight with some issues with the way we handle
DNs and its components :
- creating entries with a RDN containing two times the same AT is not
allowed by the spec
- searching for an entry which RDN is cn=Doe+gn=John does not work when
searching for
Le 2/20/12 7:36 PM, Alex Karasulu a écrit :
On Mon, Feb 20, 2012 at 6:33 PM, Emmanuel Lécharnyelecha...@gmail.comwrote:
Hi guys,
those last days, we had to fight with some issues with the way we handle
DNs and its components :
- creating entries with a RDN containing two times the same AT is
On Mon, Feb 20, 2012 at 11:59 PM, Emmanuel Lécharny elecha...@gmail.comwrote:
Le 2/20/12 7:36 PM, Alex Karasulu a écrit :
On Mon, Feb 20, 2012 at 6:33 PM, Emmanuel Lécharnyelecha...@gmail.com**
wrote:
Hi guys,
those last days, we had to fight with some issues with the way we handle
DNs
Le 2/20/12 11:20 PM, Alex Karasulu a écrit :
So, the main issue is the way AVA handles values. As soon as we *know*
what we should expect when we create an AVA, then suddenly it becomes way
easier. Basically, an AVA contains one type and one value. This value can
be a String or a byte[],
Le 2/20/12 11:58 PM, Alex Karasulu a écrit :
On Tue, Feb 21, 2012 at 12:49 AM, Emmanuel Lécharnyelecha...@gmail.comwrote:
Le 2/20/12 11:20 PM, Alex Karasulu a écrit :
So, the main issue is the way AVA handles values. As soon as we *know*
what we should expect when we create an AVA, then
On Tue, Feb 21, 2012 at 1:07 AM, Emmanuel Lécharny elecha...@gmail.comwrote:
Le 2/20/12 11:58 PM, Alex Karasulu a écrit :
On Tue, Feb 21, 2012 at 12:49 AM, Emmanuel Lécharnyelecha...@gmail.com*
*wrote:
Le 2/20/12 11:20 PM, Alex Karasulu a écrit :
So, the main issue is the way AVA
