Blogger :
MSDN Blogs
All posts :
All posts by MSDN Blogs
Category :
WSCF/WCF
Blogged date : 2008 May 12
If you are a SOA developer, Duplex message pattern would surely have grabbed your attention. Now, with WCF, it's easy to implement an architecture where both service and client can request. If you are going for netTCPBinding, underlying system identifies the inactive sockets for a certain inactivity time and closes them. While working on one of the WCF duplex implementation, I implemented TCP keep-alive mechanism (using a worker thread) to keep the channel open forever.
Client checking the health of service after each 200 secs looked great to me but the outcome was dropped socket in unnoticeable manner. After shooting all of my bullets, I came to know that the WCF duplex channel can be sustained only for 80-90 secs interval. Pulse checking after each 80 secs did the trick.... :)
Contents
ReBlogger Contents
Email TopXML