选择Windows Azure上的会话管理方式 [英] Select a way for Session Management on Windows Azure

查看:90
本文介绍了选择Windows Azure上的会话管理方式的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在计划将在Windows Azure上部署的应用程序.Web角色将具有多个实例.我发现在多个实例中 in-proc 会话将无法正常工作.我发现我可以通过以下方式来管理会话

I am planning for a application which will be deployed on Windows Azure. The web role will have multiple instances. I see that with multiple instances in-proc session will not work.I see that I have following ways to manage my session

  1. 使用Azure存储

  1. Use Azure Storage

SQL Azure

SQL Azure

AppFabric

AppFabric

我不想使用选项2(SQL Azure).

I don't want to go with option 2 (SQL Azure).

我应该选择哪个选项?

更新1

我遇到了这个

I came across this post which demonstrates session affinity on Azure with Aplication Request Routing(ARR). How about going with this option, instead of above?

推荐答案

AppFabric缓存服务.它将在30天,请查看以下链接:使用Windows Azure AppFabric缓存进行会话状态以了解如何使用它.

AppFabric Caching Service, definitely. It will be live in 30 days, take a look on this link: Using the Windows Azure AppFabric Caching for Session State in order to see how to use it.

表存储提供程序不能很好地工作,仅是概念证明,不应在生产代码中使用.

The table storage provider doesn't work very well, is just a proof of concept and should not be used in production code.

Microsoft不支持在SQL Azure中保持会话状态.此外,由于没有SQL Job Agent,因此必须将清理逻辑放入WebRole或单独的Worker角色.

Keep the session state in SQL Azure is not supported by Microsoft. Besides, since there is no SQL Job Agent, you have to put the cleaning logic in your WebRole or in a separate Worker role.

这篇关于选择Windows Azure上的会话管理方式的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆