Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
The following 2 methods defined by SyncronizationMBean have been introduced with a warning about being potentially expensive [0]:
- syncAllUsers
- syncAllExternalUsers
To me defining API that is designed with scalability issues in mind, looks like a troublesome pattern. As far as I understood from the history associated with this, I assume that it was introduced to allow for upfront sync to workaround other issues faced by sync-upon-login.
With the latest improvements and features introduced wrt to the user-sync, I think we should move forward deprecating the troublesome methods for the upcoming 1.6 release.
[0] Quote from Javadoc: "Note that this can be an expensive operation since all potential users need to be examined."