• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 834
  • Last Modified:

.Net Web Service Client and the Max number of concurrent connections

I am adding a web service client proxy to an application server (non asp.net). this server is wriiten in c# and .net framework 3.5. The client proxy will call a third party web service on another server using basichttpbinding. There could be hundreds of simultaneous client web service requests and I would like to know what on the client side are the best practices to contend with such issues like; max client connections, timeouts, asynchronous client function calls, etc...
0
lsassano
Asked:
lsassano
1 Solution
 
MlandaTCommented:
On the client side you probably only really need to use Try..Catch blocks in various places. You can also override the Timeout when calling web services and easily use asyncronous method calls when they are appropriate. There are many options for making use of these techniques. however, you may pick up some guidelines here: http://msdn.microsoft.com/en-us/library/ff647786.aspx

However, when it comes to issues like max client connections... it is actaully the server side that you need to worry about. There are various server side strategies to deal with those issues... for example: database tuning, web farms, load balancing, more efficient processing through use of appropriate coding techniques and the like.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now