有关控制 WCF PeerChannel 连接的问题

发布于 2024-08-16 22:14:53 字数 632 浏览 8 评论 0原文

我一直在研究WCF中的PeerChannel。 文档 表明对等点将自动尝试在 3 和7 个相连的邻居。

我的场景是在一个昂贵的、高延迟的连接的一侧有几个系统;以及另一侧的一个或多个。

由于连接的带宽有限,我真的很想控制这个宝贵资源上建立的连接数量。

拓扑是这样的:

                                       (c)
a    (precious bandwidth connection)    |
| <-----------------------------------> d
b            (high latency)             |
                                       (e)

1. 我真的没有什么办法可以将珍贵链路上的链路保持为一两个吗?
2. PeerChannel 在选择允许哪些邻居时会考虑延迟吗?
3. 我可以做些什么来鼓励 WCF PeerChannel 将宝贵链路上的邻居保持在最低限度?

I've been studying the PeerChannel in WCF. The docs indicate that a peer will automatically try to get between 3 and 7 connected neighbors.

My scenario is a couple of systems on one side of an expensive, high-latency connection; and one or more on the other side.

Since the connection has limited bandwidth, I'd really like to keep control of how many connections are made across this precious resource.

The topology is something like this:

                                       (c)
a    (precious bandwidth connection)    |
| <-----------------------------------> d
b            (high latency)             |
                                       (e)

1. Is there really nothing I can do to keep the links across the precious link at one or two?
2. Will the PeerChannel consider the latency when choosing which neighbors it allows?
3. Is there anything I can do to encourage the WCF PeerChannel to keep the neighbors across the precious link to a minimum?

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

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

发布评论

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

评论(1

星光不落少年眉 2024-08-23 22:14:53

正如预期的那样,程序员实际上无能为力来控制网格的构造,这可能是最好的。

我发现通过在 ab 之间建立一个网格,在 cde 之间建立一个网格,我可以实现我想要的结果。然后是一个单独的网格,其目的是充当宝贵连接上的转发器,该连接仅连接来自 ab 的 1 台主机和来自 cde 的 1 台主机。

像这样的东西:

                (AC mesh)
         a----------------------c
(AB mesh)|   (precious link)    |
         b                      d  (CDE mesh)
                                |
                                e

As expected, there is really nothing a programmer can do to control the construction of the mesh, which is probably for the best.

I figured out that I could achieve the result I wanted by having a mesh between a-b, and a mesh between c-d-e. Then a seperate mesh whose purpose is to act as a repeater across the precious connection which only connects 1 host from a-b and 1 host from c-d-e.

Something like this:

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