问题描述
从下面的内容我知道basicHttpBinding已经实现了某种会话，并且不是无状态的:
From the following I know that basicHttpBinding has implemented some kind of session and not stateless:
每次呼叫服务必须了解状态；也就是说，他们必须主动管理自己的状态，从而给客户带来连续会话的错觉.状态感知服务与无状态服务不同.实际上，如果按通话服务是真正的 无状态的，一开始就不需要按呼叫激活.
Per-call services must be state-aware; that is, they must proactively manage their state, giving the client the illusion of a continuous session. A state-aware service isn't the same as a stateless service. In fact, if the per-call service were truly stateless, there would be no need for per-call activation in the first place.
粘贴自< http://codeidol.com/csharp/wcf/Instance-Management/Per-Call-Services/ >
Pasted from <http://codeidol.com/csharp/wcf/Instance-Management/Per-Call-Services/>
实际上，basicHttpBinding的operationcontext中的sessionid为null，所以我想知道:basicHttpBinding是否存在?支持状态?
Actually, the sessionid in operationcontext of basicHttpBinding is null, so I am wondering: Does basicHttpBinding support state?
- 如果是，则与其他绑定(如wsHttpBinding)有任何区别.
- 如果没有，如何将接收超时保持为10分钟.
顺便说一句，我尝试实现一个看门狗解决方案，以使会话始终在客户端和服务器端服务之间保持活动，并使用basicHttpBinding.
BTW,I try to implement a watch dog solution to keep the session always alive between client and server side service and using basicHttpBinding .
我们知道，basicHttpBinding的默认接收超时为10分钟，但是在我的应用程序中，它在10分钟后不会超时.为什么?
As we know, the default receive timeout of basicHttpBinding is 10 minutes, but in my application, it doesn't timeout after 10 minutes. Why?
非常感谢您提前提供的大力帮助，我们非常感谢您提出的任何想法.
Many thanks for your great help in advance, any ideas are highly appreciated.
Yuanzi
推荐答案
http://codeidol.com/csharp/wcf/Instance-Management/Per-会话服务/
这篇关于basicHttpBinding如何支持状态(receivetimeout)?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！