Hi,
long time, no see :)
I have a proposal about the way we handle the operation results.
Currently, every operation is returning a Response, and if we want to
know if the operation has been successful, we have to check the
LdapResult field. This is not very convenient.
Assuming that when
Hi Emmanuel,
Long time no hear!
I think this is a good idea. It's what we chose to do in the OpenDS SDK
and I think that it makes the API much more usable in practice.
Application code is leaner and less error prone since there is no need
to check (or forget to check!) the result code after
On 7/19/10 7:02 PM, Matthew Swift wrote:
Hi Emmanuel,
Long time no hear!
I think this is a good idea. It's what we chose to do in the OpenDS
SDK and I think that it makes the API much more usable in practice.
Application code is leaner and less error prone since there is no need
to check (
hello guys,
On Mon, Jul 19, 2010 at 10:48 PM, Emmanuel Lecharny wrote:
After a discussion on IRC we have decided to inject LdapResult object
into the LdapException.
Another significant choice was not to throw exceptions for the result codes
3(timeLimitExceeded) and 4(sizeLimitExceeded) related
On Thu, Jul 22, 2010 at 12:37 PM, Kiran Ayyagari wrote:
> hello guys,
>
> On Mon, Jul 19, 2010 at 10:48 PM, Emmanuel Lecharny
> wrote:
>
>
> After a discussion on IRC we have decided to inject LdapResult object
> into the LdapException.
> Another significant choice was not to throw exceptions f
