Comments on: More details on MaxConnections http://kennyw.com/work/indigo/181 Kenny Wolf Thu, 02 Feb 2012 02:21:15 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Does NetTcpBinding.MaxConnections limit the number of concurrent connections to an endpoint or…? | DeveloperQuestion.com http://kennyw.com/work/indigo/181/comment-page-1#comment-222276 Does NetTcpBinding.MaxConnections limit the number of concurrent connections to an endpoint or…? | DeveloperQuestion.com Tue, 09 Nov 2010 20:27:36 +0000 http://kennyw.com/indigo/181#comment-222276 [...] the following blog http://kennyw.com/work/indigo/181 claims this property this property doesn’t limit the number of concurrent connections, but [...] [...] the following blog http://kennyw.com/work/indigo/181 claims this property this property doesn’t limit the number of concurrent connections, but [...]

]]> By: Gerry http://kennyw.com/work/indigo/181/comment-page-1#comment-198125 Gerry Wed, 31 Mar 2010 13:52:12 +0000 http://kennyw.com/indigo/181#comment-198125 Hello, MaxConnections is relevant on client side? Or it's important on client side only if the service callback it? Hello,

MaxConnections is relevant on client side? Or it’s important on client side only if the service callback it?

]]> By: Ron http://kennyw.com/work/indigo/181/comment-page-1#comment-103592 Ron Mon, 12 May 2008 06:25:08 +0000 http://kennyw.com/indigo/181#comment-103592 :) Hi kenny, the end of this story was my bug , that make the host of the channel to re-create and re-create also the channel , combine this with the stream vs buffer , made a lot of sockets... reparing the bug + using bufferd channel solve the problem. thanks for your help :)
Hi kenny,
the end of this story was my bug , that make the host of the channel to re-create and re-create also the channel , combine this with the stream vs buffer , made a lot of sockets…
reparing the bug + using bufferd channel solve the problem.
thanks for your help

]]> By: Kenny http://kennyw.com/work/indigo/181/comment-page-1#comment-101283 Kenny Sat, 03 May 2008 18:35:01 +0000 http://kennyw.com/indigo/181#comment-101283 The reason you don't see this for buffered is that each buffered channel maps to a single socket. For Streaming, each active request-reply maps to a socket. I bet you have a bunch of simlutaneous calls to channel.[Begin]Send which is why you are seeing the new TCP sockets in process explorer. Is that a correct assessment? The reason you don’t see this for buffered is that each buffered channel maps to a single socket. For Streaming, each active request-reply maps to a socket. I bet you have a bunch of simlutaneous calls to channel.[Begin]Send which is why you are seeing the new TCP sockets in process explorer. Is that a correct assessment?

]]> By: Ron http://kennyw.com/work/indigo/181/comment-page-1#comment-94070 Ron Tue, 18 Mar 2008 16:26:19 +0000 http://kennyw.com/indigo/181#comment-94070 First, Thanks for your answer. In my code, I try to: (In first time) 1. Create channelfactory 2. Create channel 3. Open this channel 4. Make the req-res (stream) Then in the second call (very little time after) I am looking if I already have the channel, and if it's State is opened In this case I take the channel and use it again to make the req-res In case than the channel is not opened, I will re-create it, and opened it what's happen is when I use this approach , I succeeded to make the all req-res , but , every time I saw new tcp socket connection (in process explorer tcp view) in both sides (client & server) Play with the binding maxConnections does not help (both sides tests) Only when moved to TransferMode.Buffered its work using the same socket. Kenny, I following your blog and I'll be happy to show you the code :) But via e-mail... Thanks again Ron First, Thanks for your answer.
In my code, I try to:
(In first time)
1. Create channelfactory
2. Create channel
3. Open this channel
4. Make the req-res (stream)

Then in the second call (very little time after)
I am looking if I already have the channel, and if it’s State is opened
In this case I take the channel and use it again to make the req-res

In case than the channel is not opened, I will re-create it, and opened it

what’s happen is when I use this approach , I succeeded to make the all req-res , but , every time I saw new tcp socket connection (in process explorer tcp view) in both sides (client & server)
Play with the binding maxConnections does not help (both sides tests)
Only when moved to TransferMode.Buffered its work using the same socket.

Kenny, I following your blog and I’ll be happy to show you the code :)
But via e-mail…

Thanks again
Ron

]]> By: Kenny http://kennyw.com/work/indigo/181/comment-page-1#comment-93885 Kenny Mon, 17 Mar 2008 17:37:06 +0000 http://kennyw.com/indigo/181#comment-93885 On the client, the way to control this is to throttle the amount of [Begin]Send calls you make simultaneously. On the server-side, you can control the number of connections through a combination of Service-level throttles and tcpBindingElement.MaxConnections On the client, the way to control this is to throttle the amount of [Begin]Send calls you make simultaneously. On the server-side, you can control the number of connections through a combination of Service-level throttles and tcpBindingElement.MaxConnections

]]> By: Ron http://kennyw.com/work/indigo/181/comment-page-1#comment-93822 Ron Mon, 17 Mar 2008 09:20:59 +0000 http://kennyw.com/indigo/181#comment-93822 Hi Kenny, how I can avoid opening multiple tcp connections when using TransferMode.Streamed ? with many calls to the same service ? I want to enjoy both worlds: streaming (large data transfer) & control the number of opened connections (if I already have open one...) In my app , I'm using the same channel for multiple receives , but still I see many connections opened (process explorer - tcp view at both client and server) Thanks Hi Kenny,
how I can avoid opening multiple tcp connections when using TransferMode.Streamed ? with many calls to the same service ?
I want to enjoy both worlds: streaming (large data transfer) & control the number of opened connections (if I already have open one…)
In my app , I’m using the same channel for multiple receives , but still I see many connections opened (process explorer – tcp view at both client and server)
Thanks

]]>