更新时间:2022-10-22 20:43:01
是的,这是我们文档中的建议之一: http://msdn.microsoft.com/en-us/library/gg437468.aspx
(我们文档中的摘录)
有多种方法可以解决大量持久订阅的问题,导致Lync Server 2010出现错误响应。
由于限制适用于每个端点,因此应用程序可以创建多个观察程序端点来分配负载。
由于限制适用于每个Lync Server 2010池,因此管理员可以跨多个池分配用户以分配负载。
作为处理大量订阅的***做法,它建议UCMA 3.0应用程序限制其订阅的类别数量。这可以通过在创建端点时提供过滤器来实现。通过限制
类别数量,允许更多订阅。
(Maybe this is the right place for this question?)
I know the limit for the number of simultaneous presence subscriptions is there for a reason, it would give a too high performance hit if 10000 people each persistently subscribed to all the other 9999. But here we want just *one*, our application, to subscribe to everyone.
It seems Lync Server has simplified matters with Application Endpoints compared to OCS, being a "Trusted Application" opens the doors. I know an application can have multiple endpoints, but I wonder if this can be used in the way I think:
Yep, that's one of our recommendations in our documentation: http://msdn.microsoft.com/en-us/library/gg437468.aspx
(snippet from our documentation)
There are several ways to deal with the problem of a large number of persistent subscriptions, resulting in an error response from Lync Server 2010.
Because the limit is for each endpoint, the application can create multiple watcher endpoints to distribute the load.
Because the limit is for each Lync Server 2010 pool, the administrator can distribute users across multiple pools to distribute the load.
As a best practice for dealing with a large number of subscriptions, it is recommended that a UCMA 3.0 application limit the number of categories it subscribes to. This can be accomplished by supplying a filter when the endpoint is created. By limiting the number of categories, more subscriptions are allowed.