-
Suggestion
-
Resolution: Fixed
-
None
-
None
Currently we cache calls made in atlassian-user and os-user to improve the user manager layer of Atlassian products.
It would make sense to push the caching responsibility down the stack (to the Crowd client layer) so that:
- caching code doens't need to be duplicated
- all applications using the Crowd client can take advantage of the "free" caching
- it allows us to develop an event driven cache in the future to further improve performance of all applications using the Crowd client.
- is related to
-
CWD-763 Crowd client libraries for JIRA using AD with SSL enabled are unacceptably slow.
-
- Closed
-
-
CWD-536 JIRA performance improvements
- Closed
- relates to
-
CWD-772 Crowd client libraries and caching need further review to improve JIRA performance
- Closed
- was cloned as
-
CWD-1037 Investigate caching the domain value for the cookie
- Closed
[CWD-614] Implement caching on Crowd client layer
Workflow | Original: JAC Suggestion Workflow [ 3389104 ] | New: JAC Suggestion Workflow 3 [ 3629551 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1391237 ] | New: JAC Suggestion Workflow [ 3389104 ] |
Assignee | Original: David O'Flynn [Atlassian] [ doflynn ] | |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Crowd Development Workflow v2 [ 272937 ] | New: Simplified Crowd Development Workflow v2 [ 1391237 ] |
Workflow | Original: Feature Request Workflow [ 174159 ] | New: Crowd Development Workflow v2 [ 272937 ] |
Workflow | Original: jira [ 117529 ] | New: Feature Request Workflow [ 174159 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Remaining Estimate | New: 0h [ 0 ] | |
Time Spent | New: 80h [ 288000 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |