Open Bug 76785 Opened 24 years ago Updated 7 years ago

design/implement a timeout strategy for LDAP XPCOM SDK

Categories

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

Product:
Directory
Component:
LDAP XPCOM SDK
Type:
defect

Tracking

(Not tracked)

Milestone:
Future

People

(Reporter: dmosedale, Unassigned)

References

(Blocks 1 open bug)

Details

We need to support operations being timed out, and the timeout being communicated back through nsILDAPMessageListener.
Blocks: 76755
Blocks: 17880
No longer blocks: 17880
Status: NEW → ASSIGNED
Severity: normal → major
Priority: -- → P2
Target Milestone: --- → mozilla0.9.1
reassign Olga as QA cintact
QA Contact: yulian → olgac
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Blocks: 78232
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Priority: P2 → P4
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Target Milestone: mozilla0.9.4 → mozilla1.0
Target Milestone: mozilla1.0 → mozilla0.9.8
We may get some help from this by upgrading to a newer version of the LDAP C SDK; I'm not sure.
Assignee: leif → dmose
Status: ASSIGNED → NEW
OS: Linux → All
Hardware: PC → All
Target Milestone: mozilla0.9.8 → mozilla0.9.9
Moving out based on the priority.
Status: NEW → ASSIGNED
Target Milestone: mozilla0.9.9 → Future
Assigning bugs that I'm not actively working on back to nobody; use SearchForThis as a search term if you want to delete all related bugmail at once.
Assignee: dmose → nobody
Status: ASSIGNED → NEW
Filter on "Nobody_NScomTLD_20080620"
Assignee: nobody → dmose
QA Contact: olgac → xpcom
Assignee: dmose → nobody
You need to log in before you can comment on or make changes to this bug.