为每个webuser创建一个UserEndpoint或创建一个为每个webusers服务的UserEndpoint？ [英] Create a UserEndpoint per webuser or create a single UserEndpoint that serve every webusers?

问题描述

您好，我需要创建一个WCF服务，以将网络客户端（没有SIP URI）与OCS Presence集成。用户必须对服务进行身份验证，并且每个请求都会检索指定用户的存在（通过基于查询的状态或先前对状态用户的服务订阅）。 

Hello, i need to create a WCF Service to integrate webcustomers (dont have a SIP URI) with OCS Presence. Users must authenticate to the service and every request retrieves the presence of the user specified (througth a query based presence or a previous subscription of the service to the presence user). 

推荐答案

从效率的角度来看，两种方法可能大致相同。 在任何一种情况下，进出"用户"的所有网络流量都来自"用户"。通过你的WCF服务，这是一个洗涤。 对于具有多个呼叫的单个用户，状态信息量略低，但不是太大。  OCS服务器上的状态也大致相同，我认为这也是一种清洗。

主要问题是您需要在应用程序中做多少工作来跟踪状态和让对话保持有效。 

顺便说一下，看看微软发布的这个样本。它实现了一个WCF服务，该服务使用UCMA来支持对OCS的访问，其功能与OCS 2007 R1中提供的CWA AJAX大致相同。 它可能会为您节省大量的工作。

UCMA 2.0 WCF接口 - 主页

From an efficiency point of view, either approach is probably about the same.  In either case all the network traffic to and from the "users" goes through your WCF service so that's a wash.  The amount of state information is a little lower with the single user with multiple calls, but not too significant.  The state on the OCS server is also roughly the same and I think that's a wash as well.

The main issue is how much work you need to do in your app to keep track of the state and to keep the conversations working. 

By the way, take a look at this sample that Microsoft published. It implements a WCF service that uses UCMA to support access to OCS with roughly the same level of functionality as CWA AJAX provided in OCS 2007 R1.  It might save you a lot of work.



UCMA 2.0 WCF Interface - Home

这篇关于为每个webuser创建一个UserEndpoint或创建一个为每个webusers服务的UserEndpoint？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！