0

So I create NetTcpBinding on both sever and client side (in a runtime), but how will connection behave in case of configuration conflicts? E.g. if on server I have 

binding.ReliableSession.Enabled = true;

and I forget to put same lines on client side, would the reliable session actually be working?

Edit: to rephrase, in case of any binding and any binding property, if they differ on server and client, which one will be used in work?

athabaska
  • 455
  • 3
  • 22

1 Answers1

1

NetTcpBinding does not enable a reliable session by default. So although your endpoint supports a reliable session, it will not use a reliable session if it is not used/enabled by the client.

This feature needs to be configured in the configuration files for the client and service if a reliable session is required.

Bruce Adams
  • 12,040
  • 6
  • 28
  • 37
  • Thank you, that's important notice. But I mostly need to know how conflicts in cofigurations would be solved by framework – athabaska Mar 04 '15 at 08:21
  • I don't believe there is a conflict. By enabling reliableSession on your endpoint you are able to initiate a reliable session with clients who have enabled the feature. – Bruce Adams Mar 04 '15 at 08:34
  • ReliableSession is just an example. What if I have different timeout values, which one will be used? – athabaska Mar 04 '15 at 08:38
  • I don't think it's very straight forward with a general rule that can be applied to all attributes. Specifically, I believe timeouts will default to whichever times out first. Here is some good information that you should find useful: http://stackoverflow.com/questions/4879310/when-setting-up-a-wcf-client-and-server-how-synchronized-does-the-config-files – Bruce Adams Mar 04 '15 at 09:00