Current filter:
                                You should refresh the page.
                                  • 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

                                • Simon de Kraa 10.16.2012

                                  The ASP.NET provider model enables developers to choose from three session providers: InProc, StateServer and SQLServer. With Windows Azure caching, a fourth session provider is technically available, but be careful not to confuse session with cache. Cache is about improving performances, session is about making an application stateful.
                                  The Windows Azure caching session provider for ASP.NET uses its distributed—and potentially highly available—cache as a repository for ASP.NET sessions. This is transparent and available without breaking existing code. Having such a provider enables an ASP.NET session to survive if the Web server crashes or goes offline, because sessions are stored out-of-process in the Windows Azure cache.

                                1 Solution

                                Creation Date Importance Sort by

                                Hello Simon,
                                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.

                                • Simon de Kraa 10.17.2012

                                  Ok, I understand. But looking at you are quite decisive that you cannot use other than InProc. So for example a database is not an option. But you cannot say this off the top of your head for Windows Azure cache? Thanks.

                                • Dennis (DevExpress) 10.17.2012

                                  Simon, at the time that reply was given, no "Windows Azure caching session provider" option was taken into account. Generally, I can only guarantee 100% things that we have implemented in our code, covered by unit and functional tests, described in docs, shown in demos, etc. This is not the case in case of this "Windows Azure caching session provider" as I indicated in my answer above. So, not to mislead you, I honestly said what I said above.
                                  Let me know if you require any further clarification on the subject.