|
If you were logged in you would be able to see more operations.
|
|
|
| Severity: |
Medium
|
| Environment: |
All
|
|
GroupManager is caching group roles and members by the request ID instead of by the groupID. As a result, the end user must maintain a dictionary of requestID's indexed by groupID. This is also a possible memory leak, with several duplicate group list cache's indexed by unique request ids.
|
|
Description
|
GroupManager is caching group roles and members by the request ID instead of by the groupID. As a result, the end user must maintain a dictionary of requestID's indexed by groupID. This is also a possible memory leak, with several duplicate group list cache's indexed by unique request ids. |
Show » |
|
Bug
Resolved
Minor
GroupManager caching by requestID, possible memory leak
GroupRolesCaches, GroupMembersCaches, and GroupRolesMembersCaches are now indexed by the group UUID instead of the RequestID in the request packet. This should prevent duplicate caches from existing for the same group under different request ids, as well as provide a more logical way to reference cached member/role info.