No, I don't think they help.
What I need is:
Person one visits the site by calling a Web Service. The Web service checks its object and it is null, so it checks 'somewhere' to see if there is a saved instance of the object, since there is not, it creates a new instance of the object and saves it to
'somewhere' (somewhere is what I am trying to figure out)
Person two visits the site by calling a Web Service. The Web service checks its object and it is null, so it checks 'somewhere' and finds an instance that was created when person one called the Web Service. It then grabs that instance and starts using it.
The object will be quite large (10 Mb - 15 Mb) so I don't think serialization is the answer. If I were doing this on my own server, I would create a 'Windows Service' that would host the object. However, since this will be running on Azure, first, I don't
know if I would be allowed to run a service on the Web Server, and second, since Azure could spin up & down, multiple web servers, how would I handle that?
Thanks