Session in WCF

Question

What is wshttpbinding in case of WCF persession? and what is the purpose of it?

Pravin More · Answer

Hi Prashant WSHttpBinding Defines a secure reliable interoperable binding suitable for non-duplex service contracts. It offers lot more functionality in the area of interoperability. It supports WS-* functionality and distributed transactions with reliable and secure sessions using SOAP security. It uses HTTP and HTTPS transport for communication. Reliable sessions are disabled by default. but silverlight doesnot support wshttpbinding..... i have recently written article on Session in WCF and Silverlight you can refer it. Click Here . Thank You Pravin.

Hemant Kumar · Answer

There's two things you need to consider here: if your hosting in IIS (or WAS as part of IIS7) you cannot set a base address - the base address for your service will be the virtual directory where the MyService.svc file lives. You can still set relative addresses though if you self-host you typically will add base addresses in your config so you can spare yourself having to spell out the entire address all the time (but you can - if you wish to do so). So if you have your MyService.svc inside a virtual directory called MyApp on your localhost machine and then use this config: then your old-style basicHttp service will be reachable at: http://localhost/MyApp/MyService.svc/basic and your new wsHttp driven service will be reachable at: http://localhost/MyApp/MyService.svc/wsHttp You can name those relative addresses (anything after .../MyApp/MyService.svc ) anything you like - just make sure they're different from one another. Hosting in IIS --> location (virtual directory) of your *.svc file becomes your base address. If you self-host your service inside a console app or a Windows NT Service you get to set your base addresses yourself: Now in this case your old-style basicHttp service will be reachable at: http://localhost:8185/Services/basic and your new wsHttp driven service will be reachable at: http://localhost:8185/Services/wsHttp You can define a base address for each of the transports e.g. one for http:// one for net.tcp:// and so on. And of course if you really must you can also define your complete addresses inside your element for each of the service endpoints - this gives you total flexibility (but only works in self-hosting scenarios).