I have a program, lets call it program ABC.
This program talks to a dll and return a message.
For my silverlight app, I will need to talk to this program, and receive the message. I will have different amount of silverlight clients talking to the program at the same time. It ranges from usually 10 to 100. I am currently using TCP to communicate to the program.
For now,my applications are using C# and I will be changing them to silverlight and below are my experiences.
So my concern is that I noticed slowness when there is too much connection to the program through TCP, usually at 20 - 30 connections. Right now I am using async for the TCP server, and trying to use TCP connection pool to see if it helps. TCP was chosen due to the speed needed as it is only at transport level.
In the mean time, will using generic handler be better and efficient especially at high connection rate? I don't mind sacrificing a little speed at low connections, but main point is I do not want to see slowness at high number of connections. Using the TCP method, the program works like retarded when it hits around 20-30 connections.