同一个合约的两个绑定

发布于 2024-10-11 07:34:25 字数 303 浏览 3 评论 0原文

我有一份合同，其中有一个 basicHttpBinding。

            <endpoint address="http://localhost:49654/BookShopService.svc" binding="basicHttpBinding" contract="BookShop.IBookShopService">
            </endpoint>

我想使用 wsHttpBinding 添加另一个端点，以实现相同的绑定。我必须采取哪些步骤？结果地址是什么？

原文

I have a contract for which i have an basicHttpBinding.

            <endpoint address="http://localhost:49654/BookShopService.svc" binding="basicHttpBinding" contract="BookShop.IBookShopService">
            </endpoint>

I want to add another endpoint with wsHttpBinding, for the same binding.
What are the steps I have to take? What would be the resulting address?

分享到QQ

分享到微博

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

发布评论

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

厌倦 2024-10-18 07:34:25

只需添加另一个具有不同地址的终结点，它应该如下所示：

<endpoint address="http://localhost:49654/BookShopService.svc" binding="basicHttpBinding" contract="BookShop.IBookShopService">
</endpoint>
<endpoint address="http://localhost:49654/BookShopServiceWS" binding="wsHttpBinding" contract="BookShop.IBookShopService">
</endpoint>

MSDN。

Just add another endpoint with a different address, it should look like this:

<endpoint address="http://localhost:49654/BookShopService.svc" binding="basicHttpBinding" contract="BookShop.IBookShopService">
</endpoint>
<endpoint address="http://localhost:49654/BookShopServiceWS" binding="wsHttpBinding" contract="BookShop.IBookShopService">
</endpoint>

There is a primer on MSDN.

回复收藏 0 原文

妖妓 2024-10-18 07:34:25

如果您在 IIS 中运行，则不应提供完全限定的地址 - 该地址将由 IIS 确定，因此提供地址可能会导致部署问题。因此，以 Greg Sansom 的答案为基础，我建议

<endpoint address="" 
    binding="basicHttpBinding" 
    contract="BookShop.IBookShopService" /> 
<endpoint address="ws" 
    binding="wsHttpBinding" 
    contract="BookShop.IBookShopService" />

其中 ws 是服务位置的相对地址。

例如

http://localhost:49654/BookShopService.svc - basicHttp 端点
http://localhost:49654/BookShopService.svc/ws - wsHttp 端点

If you are running in IIS, then you shouldn't supply a fully qualified address - the address will be determined by IIS and so supply one can cause deployment problems. So, using Greg Sansom's answer as a foundation, I'd suggest

<endpoint address="" 
    binding="basicHttpBinding" 
    contract="BookShop.IBookShopService" /> 
<endpoint address="ws" 
    binding="wsHttpBinding" 
    contract="BookShop.IBookShopService" />

where ws is a relative addresses to the service location.

e.g.