Suggested Videos
Part 14 - Risks of implementing IExtensibleDataObject interface
Part 15 - Exception handling in WCF
Part 16 - SOAP faults in WCF
This is continuation to Part 16. Please watch Part 16, before proceeding.
An unhandled exception in the WCF service, will cause the communication channel to fault and the session will be lost. Once the communication channel is in faulted state, we cannot use the same instance of the proxy class any more. We will have to create a new instance of the proxy class.
BasicHttpBinding does not have sessions. So when there is an unhandled exception, it only faults the server channel. The client proxy is still OK, because with BasicHttpBinding the channel is not maintaining sessions, and when the client calls again it is not expecting the channel to maintain any session.
WSHttpBinding have secure sessions. So when there is an unhandled exception, it faults the server channel. At this point the existing client proxy is useless as it is also faulted, because with wsHttpBinding the channel is maintaining a secure session, and when the client calls again it expects the channel to maintain the same session. The same session does not exist at the server channel anymore, as the undhandled exception has already torn down the channel and the session along with it.
Part 14 - Risks of implementing IExtensibleDataObject interface
Part 15 - Exception handling in WCF
Part 16 - SOAP faults in WCF
This is continuation to Part 16. Please watch Part 16, before proceeding.
An unhandled exception in the WCF service, will cause the communication channel to fault and the session will be lost. Once the communication channel is in faulted state, we cannot use the same instance of the proxy class any more. We will have to create a new instance of the proxy class.
BasicHttpBinding does not have sessions. So when there is an unhandled exception, it only faults the server channel. The client proxy is still OK, because with BasicHttpBinding the channel is not maintaining sessions, and when the client calls again it is not expecting the channel to maintain any session.
WSHttpBinding have secure sessions. So when there is an unhandled exception, it faults the server channel. At this point the existing client proxy is useless as it is also faulted, because with wsHttpBinding the channel is maintaining a secure session, and when the client calls again it expects the channel to maintain the same session. The same session does not exist at the server channel anymore, as the undhandled exception has already torn down the channel and the session along with it.
HI Venakt,
ReplyDeleteI am Aleem
Happy New Year
In your website few videos are missed on some technologies.And needed some useful videos on such technologies. Those are given as list below.please you could find and post it.
1. Threading concepts in C#.
2. C# 4.0 new feautres.
3. Tempdata concept in MVC.
4. communication between view to controllers.
5. Ado.net EntityFramework video tutorials.
6. "DataTable, DataRow" and "Transactions" in Ado.net Video Tutorial.
7. Ado.net EnityFramework video Tutorials.
8. Jquery Video Tutorials.
9. HTML 5 Video Tutorials.
Please you could post videos on your website.Hope Good response from you.
Thnaks and Regards
Aleem
Hi this is chakradhar
ReplyDeletein wcf tutorial dont have all bindings .
u explain only basic http,nettcp,wshttp only there
can u explain rest of bindings.
2) support all kind of videos(.Flv,.mp4) upload and show video on web application
if you have this type of application please post to mail.
thanking you
Hi,
ReplyDeleteAll your videos are really good. I wish if you could publish some videos on SOAP and REST, what they are individually and how they differ. it would be of great help.
Thanks,
Swati