Indeed, if the resolver is created in the static constructor of the ReportsController
class (our default implementation), it will be reused with all clients until the application gets restarted and some report information from one session may be accessible by another.
Note that the report resolver may be created also in the normal constructor to avoid this - at the cost of the corresponding additional resources.
I agree that the newly introduced UserIdentity
is a better approach for passing current user data to the report. It may be considered as further improvement along with the performance enhancement related to report rendering engine of all REST reports services using dedicated rendering thread queue (the feature that required UserIdentity
to be introduced).
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items