[英]Why is reliable messaging not enabled by default on wsHttpBinding? AND Does the server or client config have precedence?
I've been reading about reliable messaging and have a few questions that I haven't been able to find the answer to: 我一直在阅读有关可靠消息传递的信息,并且有一些我无法找到答案的问题:
Why isn't RM enabled by default in wsHttpBinding (and others as well)? 为什么默认情况下在wsHttpBinding(以及其他)中未启用RM? In what case would you not want to use reliable messaging?
在哪种情况下,您不想使用可靠的消息传递? I know in streaming scenarios it doesn't really make sense, but I can't imagine an instance where you would want to send a message/data and not receive it.
我知道在流传输方案中这没有什么意义,但是我无法想象您想要发送消息/数据而不接收消息/数据的实例。
Which config file takes precedence if the server's and a client's do not match? 如果服务器和客户端不匹配,哪个配置文件优先? I assume if they aren't both
<reliableSession enabled="true" />
RM wouldn't be working (would that cause any errors to be thrown?), but what about things like ordered
and inactivityTimeout
? 我假设如果它们都不都是
<reliableSession enabled="true" />
RM不会起作用(会引发任何错误吗?),但是ordered
和inactivityTimeout
这样的事情呢?
Unless both server and client have set <reliableSession enabled="true" />
and session is not enabled on the server, it will not use reliable messaging. 除非服务器和客户端都设置了
<reliableSession enabled="true" />
并且未在服务器上启用会话,否则它将不会使用可靠的消息传递。
I try avoiding reliable messaging because of its overhead. 由于其开销,我尝试避免可靠的消息传递。 As far as I am concerned, if an operation is
TwoWay
, successful reply will guarantee delivery - although not the other way around always true. 就我而言,如果一个操作是
TwoWay
,成功的答复将保证交付-尽管并非总是如此。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.