blocks|key|1620844|text|例如，当您的应用程序可能在计算机场中运行，而您不能将会话配置为使用sql+server时(或者使用sql+server会对性能造成太大的影响)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1620845|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For example when your application might be running in a computer farm and you can't configure session to use sql server.( Or using sql server is too much of a performance hit)

blocks|key|1620935|text|会话用完，视图状态不会-您可以在一小时后返回，视图状态仍然可用。当您在网站上后退/前进、会话更改时，视图状态也始终可用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1620936|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Sessions run out, Viewstate does not - you can go back an hour later and your viewstate will still be available. Viewstate is also consistently available when you go back/forward on the website, Session changes.

blocks|key|1620974|text|你正在做的应用程序中，视图状态膨胀在很大程度上不是问题，那么最好将页面特定的数据存储在视图状态中，因为这有助于服务器更好地执行。如果你为会话或任何缓存而疯狂，那么你可能会伤害到自己而不是帮助自己。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1620975|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You are doing an app where viewstate bloat, for the most part, is not an issue, then it's better to store page specific data in the viewstate because it helps your server perform better. If you go crazy with session, or any caching, for that matter, you can hurt yourself more then you help yourself.

blocks|key|1406247|text|ViewState本质上只是一个隐藏的输入，必须上传到服务器并在每次请求时进行解析。此字段通常是自动填充的，通常是在程序员毫无察觉的情况下自动填充的，并且可能会变得非常大。对于许多网站来说，这是一个问题，因为即使是宽带用户的上行带宽也非常有限。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1406248|在所有用户都可以通过高速LAN访问服务器，但可用于保存会话数据的ram有限的intranet站点上，它可能更有意义。|1406249|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

ViewState is essentially just a hidden input that must be uploaded to the server and parsed with each request. This field is typically populated automatically, often with the programmer blissfully unaware, and can grow quite large. For many sites that presents a problem, because even broadband users have very limited upstream bandwidth. 

On intranet sites where all the users have high-speed LAN access to the server but the ram available for holding session data is limited, it may make more sense.

blocks|key|1621088|text|不是你问题的答案，但你的一个假设是不正确的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1621089|可以在URL中传递会话in。会话不需要cookies。|1621090|http://msdn.microsoft.com/en-us/library/aa479314.aspx|offset|length|1621091|<sessionState+cookieless="true"+/>|code-block|syntax|javascript|1621092|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|1H|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|H|3|I|5|J|7|Z|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|E]]]]

Not an answer to your question but one of your assumptions is incorrect.

Session IDs can be passed in the URL. Session does not require cookies.

<a href="http://msdn.microsoft.com/en-us/library/aa479314.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/aa479314.aspx</a>

<pre><code>&lt;sessionState cookieless="true" /&gt;
</code></pre>

blocks|key|1406373|text|ViewState和Session具有不同的作用域。ViewState被设计为在“回发”期间存储或多或少的瞬态数据，而session用于保存关键的会话状态数据。我建议对与特定的“页面会话”相关的状态使用ViewState。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1406374|如果您不喜欢ViewState的正常行为，可以非常简单地编写您自己的PageStatePersister并让这个对象执行持久性，例如使用session或Memcached之类的东西。然后，您可以完全覆盖默认的持久性机制。|1406375|然后，好事情是你可以无缝地继续使用.NET框架中的标准web控件，它将全部使用视图状态/控件状态来处理这种类型的数据，而不会使ViewState变得臃肿。服务器内存持久化机制可能非常有效。|1406376|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

ViewState and Session have different scopes. ViewState is designed to store more or less transient data, during "postbacks", while session is used to save critical session state data. I recommend using ViewState for state related to a specific "page session".

If you don't like the normal behavior of ViewState, it's pretty simple to write your own PageStatePersister and let this object perform persistence, for instance using session, or something like Memcached. You can then completely override the default persistence mechanism.

Then, the good thing is you can seamlessly continue to use standard web controls in the .NET Framework, which will all use ViewState/ControlState for this type of data, without bloating the ViewState. A server memory persistence mechanism could be very efficient.

blocks|key|1621214|text|视图状态或会话的全部原因是将web从无状态系统转变为动态的、定制的体验。当用户请求页面时，您可以从用户体验中断的地方恢复的唯一方法是记住服务器或用户客户端上的状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1621215|Viewstate是一种在客户端记住用户状态的机制。会话是一种记住服务器上用户状态的机制。|1621216|视图状态是一种瞬时存储机制。使用viewstate的控件将其状态作为隐藏输入呈现到html页中。为了防止篡改，它被签名。但是，它没有加密，所以您可能希望避免在其中放置任何敏感内容。在需要跨多个请求序列(页面加载)进行发布的情况下，视图状态非常有用。例如，当一个表单因为用户输入了错误的电子邮件地址或其他原因而无法验证时，您希望将表单恢复为用户提交之前的状态。这样做的缺点是，视图状态是一个饥饿的野兽，可以很容易地增加30-50%25的页面大小。|1621217|另一方面，会话存储在服务器上。客户端得到一个令牌，它告诉服务器哪个内存块是他们的。这可能比视图状态更安全，因为数据不会一遍又一遍地重新传输给用户。不过，这是有权衡的。您的服务器可能会内存不足。或者，如果他们的会话中断，用户可能会丢失数据。|1621218|一般来说，没有“正确”的答案可以使用。这一切都与你试图实现的目标有关。|1621219|对控件执行的大多数操作都应该使用视图状态。但是，如果您正在处理敏感信息，请考虑使用会话。如果您有一组特定页面的数据，请使用viewstate。如果在用户访问你的站点的整个过程中都需要这些数据，请考虑会话。|1621220|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

The whole reason for Viewstate or Session is to turn the web from a stateless system into a dynamic, customized experience. When a user requests a page, the only way you can resume where the user left off in their experience is to remember the state either on the server or on the user's client.

Viewstate is a mechanism for remembering the user's state on the client.
Session is a mechanism for remembering the user's state on the server.

Viewstate is a transient storage mechanism. Controls that use viewstate have their state rendered into the html page as a hidden input. To prevent tampering, it is signed. It is not encrypted, however, so you probably want to avoid putting ANYTHING sensitive in there. Viewstate is useful for situations where you want to post across series of multiple requests (page loads). An example of this is when a form doesn't validate because maybe the user entered a bad email address or something, and you want to restore the form as it was before the user submitted. The downsides to this is that viewstate is a hungry beast and can easily add 30-50% to page size.

Session, on the other hand, is stored on the server. The client gets a token that tells the server which block of memory is theirs. This can be much more secure than viewstate because the data isn't being retransmitted to the user over and over. There are trade-offs though. Your server can run out of memory. Or, the user could lose the data if their session is disrupted.

Generally, there's no "right" answer on which to use. It is all about what you are trying to accomplish. 

Most things to do with controls should use Viewstate. IF you're dealing with sensitive information however, consider Session. If you have data that is for a specific set of pages, use viewstate. If it is data that you will need throughout a user's visit on your site, considier Session.

blocks|key|1406505|text|不是真正直接回答你的问题，但它可能会解决你的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1406506|您可以存储viewstate服务器端，消除客户端的有效负载。|1406507|在inherits页面中创建一个类，并覆盖PageStatePersister。http://msdn.microsoft.com/en-us/library/system.web.ui.sessionpagestatepersister.aspx|offset|length|1406508|+public+class+RussPage+:+Page
++++{
+++++++++protected+override+PageStatePersister+PageStatePersister
++++++++{
++++++++++++get
++++++++++++{
++++++++++++++++return+new+SessionPageStatePersister(Page);
++++++++++++}
++++++++}
++++}|code-block|syntax|javascript|1406509|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.web.ui.sessionpagestatepersister.aspx^0|0|0|14|2C|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@$F|X|G|Y|1|Z]]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Not really a direct answer to your question, but it may resolve your issue.

You can store viewstate server side, eliminating the payload for the client.

Create a class the inherits page, and override the PageStatePersister.
<a href="http://msdn.microsoft.com/en-us/library/system.web.ui.sessionpagestatepersister.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/system.web.ui.sessionpagestatepersister.aspx</a>

<pre><code> public class RussPage : Page
 {
 protected override PageStatePersister PageStatePersister
 {
 get
 {
 return new SessionPageStatePersister(Page);
 }
 }
 }
</code></pre>

Other than because session storage is session-global to more than one page, why would you ever want to use the viewstate to hold values?

It seems kind of ridiculous to send any kind of information other than a few small query string like values, back and forth from the client to server. I mean what a waste of bandwidth(!), simply for storage purposes. The session, while global across multiple pages, seems like a completely superior alternative to the viewstate. 

Especially with asp.net ajax controls and variants, the viewstate could quickly become bloated tracking the various states and variables of all those different controls and html elements.

But then why is there viewstate storage for page variables and objects at all?

Maybe I'm missing another great usage for the page's viewstate storage, does anyone know something out there?

Thanks for reading!

EDIT: Everyone had a great answer, sorry if I didn't pick yours.

Why would you ever use asp.net's ViewState storage object over the Session storage object?

数据存储

服务器

除了因为会话存储对于多个页面是会话全局的，为什么还要使用视图状态来保存值呢？在客户机和服务器之间来回发送除了几个小查询字符串之外的任何类型的信息似乎都有些荒谬。我的意思是，仅仅为了存储目的，这是多么浪费带宽(！)。虽然会话是跨多个页面的全局会话，但它似乎是比视图状态更好的替代方案。特别是对于asp.net ajax控件...

问为什么要使用ASP.Net的ViewState存储对象而不是Session存储对象呢？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么要使用ASP.Net的ViewState存储对象而不是Session存储对象呢？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么要使用ASP.Net的ViewState存储对象而不是Session存储对象呢？
EN