[SSSD] LDAP connection tracking, sharing and fail-over retry framework

Simo Sorce ssorce at redhat.com
Thu Jul 8 17:21:57 UTC 2010


On Wed, 07 Jul 2010 08:43:41 -0400
Stephen Gallagher <sgallagh at redhat.com> wrote:

> > Another reason to have sdap_id_op as separate tear is caching
> > strategy: it would ineffective if LDAP connection was dropped in
> > the middle of multi-stage operation, that could be the case if
> > connection usage tracking is done within sdap_generic_send. Using
> > higher level tear ensures that connection is available through
> > complete operation, not just within single stage.  
> 
> Yeah, I think I agree with you here.

Sorry I don't see how it differs here.
If sdap_generic_send() is always restarted when the connection drops
you have exactly the same effect. If it can't be restarted you again
have the same effect, the upper level operation will fail with an error.

What am I missing here ?

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York



More information about the sssd-devel mailing list