Hi, Sorry for not getting back soon - working away. Yes the web service is in the same solution as the main web app. There is only one app pool on the machine so I assume that they would both be using that and yes it's the webservice that trying to access cache objects created by the app. I do see that each time the web service is called it gets a new session and cache ID and the object count in both is zero.
Thanks for you reply. On Sep 15, 4:50 pm, Andrew Badera <[email protected]> wrote: > The service and the app are all part of the same project? Same application > pool? > > Is the application pool recycling between data being sent tocache, > and the attempt to retrieve fromcachein the service? > > There's no trick here -- thecacheis accessible across the > application, wherever the context is available. Same app, same app > pool, samecache. > > ∞ Andy Badera > ∞ +1 518-641-1280 > ∞ This email is: [ ] bloggable [x] ask first [ ] private > ∞ Google me:http://www.google.com/search?q=andrew%20badera > > > > On Tue, Sep 15, 2009 at 10:23 AM, nik <[email protected]> wrote: > > > hi guys, > > > I'm trying to develop a web service that requires access to the > > httpcontent currentcacheused by the calling web application. Is this > > even possible? If so how do I go about doing it? > > > The calling application uses the HttpContent.Currentcacheand posts > > data to it via the .Insert and retrieves is via the .Get methods. > > > When I call the web service thecacheseems to be empty and I can't > > access the elements posted to it by the calling web app. Is there a > > way to persist the cached data between the two? I understand that > > this may not be possible as web services are aren't used in this > > manner. > > > Thanks for your time.- Hide quoted text - > > - Show quoted text -
