Reputation: 4387
A webservice i'm working with sends back a result set that equates to around 66980 lines of XML, .net returns this as a list object.
As the user journey requires that we can reload this set if they step back a page, whats the fastest/best way of storing this result set per-user without slowing everything down.
Ta
-- many solutions: http://msdn.microsoft.com/en-us/magazine/cc300437.aspx
Upvotes: 1
Views: 1056
Reputation: 161831
I'll just note here that your issue is not unique to web services. You might as easily have retrieved that list from a database, and you'd still want to cache it so you don't have to go to the database again.
Upvotes: 0
Reputation: 18649
Save it to HttpContext.Current.Cache, keyed on the user id, possibly something like "MyXml_UserId".
Upvotes: 1
Reputation: 15935
I would use memcache as a general way of caching queries. Best is that it works across nodes (in case you have more webservers).
Upvotes: 1