Caching gotcha in azure

If you access a web role from different URLs do not expect the role to be able to read the cache OR the session if it was set by calling a method from a different URL/ server name even if it points to the same thing.

Weird. For session I can understand - can't figure out why it does not work for memory in a dedicated cache role though.

[Update] I was wrong, not working with cache because there was a condition checking for session before setting the cache value. So cache value never got set. Makes sense now.

Comments

Popular posts from this blog

Tutorial: Using Google Cloud Storage from C# and .NET

Late 2008 Macbook only giving 1.5 gb/s speed with 6 gb/s Intel SSD?

The ridiculous interview experience