Where did the "Connections" property go? #231
-
|
Upgraded an old build from 4.1.0 to 4.2.2. Grapevine.Server.RestServer no longer has this property, to limit the max number of connections. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
That property had been deprecated since by 4.1.0.0 and was removed in 4.2. Specifically, between 4.0.0.195 and 4.0.0.252 I switched from my previous, clumsy attempt to manage my own thread pool to using I allowed the property to perpetuate after this for backwards compatibility, but I added the obsolete attribute, as it no longer did anything. |
Beta Was this translation helpful? Give feedback.
-
|
By that, you're saying I don't need to worry about this anymore? What if I wanted to limit the number of Connections? Is there a reason to do that still? |
Beta Was this translation helpful? Give feedback.
-
|
You don't need to worry about this anymore in Grapevine. I can't think of a reason to continue limiting the number of connections. However, if that is a feature that you like to see added back in, I can move this discussion over to the ideas board, and we can figure out an approach. |
Beta Was this translation helpful? Give feedback.
That property had been deprecated since by 4.1.0.0 and was removed in 4.2.
Specifically, between 4.0.0.195 and 4.0.0.252 I switched from my previous, clumsy attempt to manage my own thread pool to using
ThreadPool.QueueUserWorkItem, which does a much better job at it than I. TheConnectionsproperty was used in conjunction with the number of processors available to determine the size of the thread pool.I allowed the property to perpetuate after this for backwards compatibility, but I added the obsolete attribute, as it no longer did anything.