我一直在阅读有关可靠消息传递的内容，但有几个问题无法找到答案：
-
为什么 wsHttpBinding （以及其他）中默认情况下不启用 RM？在什么情况下您不想使用可靠的消息传递？我知道在流场景中这并没有什么意义，但我无法想象您想要发送消息/数据而不接收它的实例。
-
如果服务器和客户端的配置文件不匹配，哪个配置文件优先？我假设如果它们不是 inactivityTimeout？
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)? 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?
发布评论
评论（1）
除非服务器和客户端都设置了
我尝试避免可靠的消息传递，因为它的开销。就我而言，如果操作是
TwoWay，成功的回复将保证交付 - 尽管反之亦然。Unless both server and client have set
<reliableSession enabled="true" />and session is not enabled on the server, it will not use reliable messaging.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.