为什么 wsHttpBinding 上默认未启用可靠消息传递?并且服务器或客户端配置是否具有优先权?

发布于 2024-10-22 17:31:21 字数 379 浏览 4 评论 0 原文

我一直在阅读有关可靠消息传递的内容,但有几个问题无法找到答案:

  1. 为什么 wsHttpBinding (以及其他)中默认情况下不启用 RM?在什么情况下您不想使用可靠的消息传递?我知道在流场景中这并没有什么意义,但我无法想象您想要发送消息/数据而不接收它的实例。

  2. 如果服务器和客户端的配置文件不匹配,哪个配置文件优先?我假设如果它们不是 RM 将无法工作(这会导致抛出任何错误吗?),但是像 < code>ordered 和 inactivityTimeout

I've been reading about reliable messaging and have a few questions that I haven't been able to find the answer to:

  1. 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.

  2. 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?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

み青杉依旧 2024-10-29 17:31:21

除非服务器和客户端都设置了 并且服务器上未启用会话,否则它将不会使用可靠消息传递。

我尝试避免可靠的消息传递,因为它的开销。就我而言,如果操作是 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.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文