Jan 17, 2015 12:50 PM|IbrahimIslam|LINK
While a table is quick enough, it takes several seconds to get all those records from AD. The amount of time is too long if a user just has to sort records in a gridview. So, what would be a good alternative to storing large amounts of data in an intermediate
So you are showing data in a Grid like structure, then there has to be pagination.
Thus, no matter how large your dataset is you are never going to bring whole of it at once so eliminating the need for storing it in Session.
But in some cases,
Caches can help and you can use it if it deems fit in your solution.
Just to state the options, you can also make use of cache stores like Redis or Memcached.
Maybe you'll bring 10-20 records at a time and that much latency is an acceptable minimum and same goes for sorting or other functions like filtering.
And how would I distinguish one user's data from another? Session ID?
This is dependent on how you have structured your Database schema. If you are storing them maintaining relations properly then querying with a user id can help you bring relevant data to the user.