Web Service Start Up - Spam Catcher |
29-Feb-08 12:15:50
|
d7e3032119c2@s13g2000prd.googlegroups.com:
If you need to statefully store information, have you considered caching it
in a local database?
Otherwise, you could create a stateful process (i.e. service) and fetch it
locally from there.
Lastly, there are ways to keep ASP.NET from recycling the appdomain, but it
seems a bit hackish to do:
http://weblogs.asp.net/pwilson/archive/2003/12/02/40681.aspx
--
spamhoneypot@rogers.com (Do not e-mail) |
 |
| |
Web Service Start Up - John Saunders [MVP] |
01-Mar-08 01:53:48
|
You could write a small console application that would issue the same web
service request as the users do. Run it periodically, or when the system
starts. In effect, you would be creating the first user. This user would
still see the three minute delay; he just wouldn't complain about it!
--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer |
 |
| |