Is it possible to use the Windows Azure Cache to store the XAF Session State as described in the exercise below.
The idea is to use multiple Windows Azure Web servers and reserve for example 20% of memory for Windows Azure Cache (this is one of the options that is available in Windows Azure Cache).
This Windows Azure Cache will be used to store the XAF Session State.
The Windows Azure Cache mechanism will make sure the memory will be the same on a Web servers.
In this way the Session State will be the same for all Web servers and a Sticky Session router is not necessary.
Exercise: Using the Windows Azure Caching for Session State
I am afraid we cannot answer your question because we have not tested XAF Web UI in this scenario.
In any event, I doubt that it is possible to force XAF Web UI to work in it without modifying its source code. As we discussed earlier, we store some information within the ASP.NET session (it is easy to find all places by looking for the "session[") string within the XAF source code. You can recompile our sources for your experiments and test how this will work when you store this data in other places.
Probably, these changes are not required at all and this "Windows Azure caching session provider" can handle it itself, but again, we have not tested this and can say little about it. It is up to you to see how this works. However, if you have any questions on how XAF works internally, feel free to ask us. We will be glad to help you.