Answer the question
In order to leave comments, you need to log in
IIS: how to organize simultaneous networking and servicing http requests?
When using sockets (about ~ 200 tcp clients) on the web server, the processing time for requests from the client (silverlight) to the web server increases, some of them end with a TimeoutException (the timeout has expired).
Also, when connecting to a tcp client from a web server, it is not always possible to establish a connection: System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it (here ip:port) at System.Net.Sockets .Socket.EndConnect(IAsyncResult asyncResult) at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult)
How to organize simultaneous networking and servicing http requests?
Is it necessary to move the work with sockets away from the silverlight web server (for example, to a separate service)?
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question