Closed Bug 76875 Opened 24 years ago Closed 24 years ago

Add reconnectConnection() and closeConnection() to LDAP service

Categories

(Directory :: LDAP XPCOM SDK, defect, P4)

Product:
Directory
Component:
LDAP XPCOM SDK
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: leif, Assigned: leif)

References

Details

I believe we need to add these two methods, to prepare for handling connection timeouts and reconnection events. The names might change, it's just a suggestion.
Status: NEW → ASSIGNED
Depends on: 70422
Blocks: 17880
No longer blocks: 17880
reconnectConnection is currently implemented in #70422 already. It basically forces the LDAP Service to create a new connection. This is not ideal, but we could solve some of the "reconnect" issues with bug #76782.
Depends on: 76782
|ReconnectConnection()| was already added to the |nsLDAPService|, only the closeConnection() is needed (which we might do without).
Blocks: 17880
Priority: -- → P4
Under what circumstances would someone call closeConnection?
Not sure... :) Maybe it's not needed at all. -- Leif
reconnectionConnection was implemented as part of 70422. Leif, Srilatha and I can't think of a case when closeConnection would be absolutely required, so we're closing this bug as fixed. If it turns out that we're wrong, we can always open another bug.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
reassign to Olga as QA contact
QA Contact: yulian → olgac
No longer depends on: 76782
reconnectConnection() is implemented marking as verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.