Hi Lee,
If the data object is used at webservice server-side and will be frequently
accessed after the first time it is created, I think it is reasonable to
cache it. And as for how to cache it , we have several approachs:
1. Use SessionState, this is possible for ASP.NET webserivce and will help
us store the data object per client user session. However, there're some
setting we need to pay attention, see the following MSDN article:
#Using ASP.NET Session State in a Web Service
http://msdn.microsoft.com/library/en...08062002.asp?f
rame=true
Also, for session state data, there is no expiration policy we can use, we
need to manually clear it after finishing use them or let them expire when
session timeout.
2. Use Application Cache, I prefer this approach since the ASP.NET
System.Web.Cach e provide rich functionality such as cache dependency
supports so that we can make the cached object automatically expire when
some certain dependency changes. Also. in 2.0 there comes the new Sql
Database cache dependency which is rather powerful. However, since Cache
is application scope storage, we need to manually use our own index to
separate data for individual client user.
Hope this helps.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)