From this MSDN article, I see that it says the following:
If you set the AutomaticInputSessionShutdown property to false, the
channel must be closed by some other mechanism. In this case, you must
add a custom session shutdown handler to the
InputSessionShutdownHandlers property.
What are the consequences if you don’t add a custom session shutdown handler to the InputSessionShutdownHandlers property and set the AutomaticInputSessionShutdown property to false? I have two WCF services, and they can only connect to each other, secured by certificates, and I do not want their session to ever die.
Alexandru,
The whole purpose of the
InputSessionShutdownis to allow the service to make a final response to the client indicating that the client can close it’s connection.From your description, the “client” in this case is another one of your services. As long as the “client” service can properly shutdown if the duplex session is terminated, there shouldn’t be any consequence for not providing a custom
InputSessionShutdownHandler.