Hi Mike,

First of all, the Cache is shared between all the web services configured in
the same web application and same machine.
If you are trying to use the session in a WSE filter or token manager, it
could be null because WSE runs before than the ASP.NET session module (Or
you are trying to use the Session in a web service hosted outside of the
ASP.NET worker process, for instance, a windows console). Anyway, the
purpose of the session is completely different, it does not support
different expiration rules as the cache does.
You can also try with the Enterprise Library Caching application block.

Regards,
Pablo Cibraro.

  As you said, you can use a session server to share session information in
a web farm scenario, but the purpose of the session is completely different
from the purpose of the cache. (The cache supports

Hi Mike,

The System.Web.Caching.Cache (accessed via HttpContext.Cache.Current) is a
process-wide cache. Therefore the cache is "global" to across calls to the
WSE service for the same machine (assuming you're executing the web service
within the same app pool). I say this because it possible to create multiple
instances of the web service each running under a different app pool.
However, the latter deployment scenario isn't a usual configuration.

I'm still unclear as to whether you require session or cache as their
consumer API surface design goals are entirely different. Would you please
tell me a bit more about your scenario?

Kindest regards,
Michael