I propose a change in the handling of the displayed name for user names.
My proposal uses a read-only property named "displayName" in the ActiveRecord of the user model. Currently it parses the global setting "userDisplayString" and replaces each user property named there with its current value. This gives a maximum flexibility when configuring the displayed user name (especially with formatting characters such as commas, parentheses etc.), and it allows to go just a small step from here to allow user defined display names as well.
Possible side impacts: The only change made to actual JSON communication is when requesting a user list in DEFAULT or LIST mode, because the new field displayName shows up there. This is intentional. A remote application such as the dojo front end should have an easy means to access the display name the user wishes to see. This should be done centralised in the backend, because otherwise it would mean to implement this mapping twice. The displayName field is marked as readonly, so clients should know that editing this field is useless.
Each other mapping of user id to some kind of user name is done inside the metadata section of a json request, and should not affect any client. This has not changed from Gustavos previous implementation.
Patch against revision 1852