WCF send and receive timeouts on binding

So how the sendTimeout and receiveTimeout really works? My observation says that the sendTimeout parameter is used on the client side of the communication and acts as remoteCallTimeout. receiveTimeout has no meaning on the client side of the communication.

receiveTimeout is just reversed. It is used on the server side of the communication and acts as remoteCallTimeout there. sendTimeout has no meaning on the server side of the communication.

So the conclusion is following. In our scenario, when the client application communicated to application server (remoting calls are initiated just by client app) we have to specify just sendTimeout in the client app config and receiveTimeout in the application server config.

If we would communicate also in the opposite way (remoting calls initiated both from client app and application server) we would have to fill both parameters on both sides.

Advertisements

%d bloggers like this: