Actions
Architecture #123
closed
Add asynchron request/result in LDAP search
Status:
Rejected
Priority:
5 (lowest)
Assignee:
-
Category:
Architecture - Internal libs
Target version:
Pull Request:
Effort required:
Name check:
Fix check:
Regression:
Description
Now, we are doing plain old synchrone search, which is bad : we can't add result when they come, stop in the middle of a request and get some results, etc.
A an asynchrone query/result system.
Updated by François ARMAND almost 15 years ago
- Assignee deleted (
François ARMAND) - Priority changed from 4 to 5 (lowest)
Change priority/assignement
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 24 to 18
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 18 to Ideas (not version specific)
Updated by Benoît PECCATTE over 9 years ago
- Category set to Architecture - Internal libs
Updated by Benoît PECCATTE over 9 years ago
- Related to Architecture #124: Limit request size in LDAP added
Updated by François ARMAND almost 7 years ago
- Tracker changed from User story to Architecture
Updated by François ARMAND over 4 years ago
- Status changed from New to Rejected
Closing this one. We don't want what is writen in the title. We want, for specific path, to be able to have data streaming from database to UI. But data are not stored in LDAP (not only).
So, we need to open specific ticket (if we want!) like: "when doing a node search, I want streamed results".
Actions