Hi Bala,
Welcome to the ASP.NET newsgroup.
Regarding on the user id storage, IMO, unless the application is a small
application without large user id numbers, we always recommend that store
such information in database. And even we use configuration file (xml file)
to store such info, I suggest you store it in a separate file from
web.config since it is not quite good to frequently read/write web.config
file.
BTW, if possible, you can also consider load all the IDs into memory (for
caching) in your ASP.NET webservice application(If there is no security
concern on this). Because in ASP.NET 2.0, there comes a new caching
dependeny---- SqlCacheDependency, this can help us cache the data according
to a certain database table(should use sqlserver), we can make the cached
value expired automatically when the certain table has been changed. I
think this maybe helpful in your service:
#Caching in ASP.NET with the SqlCacheDependency Class
http://msdn2.microsoft.com/en-us/library/ms178604.aspx
Hope this helps.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may
learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.