分布式ASP.Net状态服务 [英] Distributed ASP.Net State Service

问题描述

如果存在任何分布式ASP.Net状态服务替代我不知道。

I'm wondering if there exist any distributed ASP.Net State Service alternative.

会话可以被存储在是InProc，的StateService或SQL。您也可以编写自定义存储供应商。对于负载平衡（没有任何形式的粘性IP）的唯一SQL /自定义将工作。

Session can be stored in InProc, StateService or SQL. You can also write custom storage providers. For load balancing (without any form of sticky IP) only SQL/Custom will work.

有没有分布任何替代ASP.Net国家服务？我想所以每个服务器可以与其他同步。

Are there any alternative ASP.Net State Services that is distributed? I'm thinking so each server can synchronize with the others.

编辑：在回答的答案：我要找会议（）存储。分布式缓存是没有问题的，速度会做罚款分布式缓存。 ：）

In response to answers: I am looking for Session() storage. Distributed cache is not a problem, Velocity will do fine for distributed caching. :)

EDIT2：针对28：9状态服务器单点故障的问题。 SQL服务器可能不是因为所选择的模型的直接访问（即，3层），它是唯一的通过中间层进行访问。

In response to Oded: State server has the problem of single point of failure. SQL server may not be directly accessible because of the model chosen (i.e. 3-layer), it is only accessible through the middle layer.

推荐答案

我以为这就是什么是速度将要被引进到表？你可能想看看微软的AppFabric 您的需求。

I thought thats what "velocity" was going to be bringing to the table? You might want to check out Microsoft AppFabric for your needs.

编辑：结果
也许我失去了一些有关你的职位和你的编辑，但我仍然pretty肯定的AppFabric是您需要为您的 会话（） 存储。也许我错了，但它肯定似乎死在我。

Maybe I'm missing something about your post and your edit, but I'm still pretty sure AppFabric is what you need for your Session() storage. Maybe I'm wrong, but it sure seems dead on to me.

这篇关于分布式ASP.Net状态服务的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！