Print Page | Close Window

push timeout / testing

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2010
Forum Discription: For .NET 4.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=3224
Printed Date: 24-Jan-2026 at 9:29am


Topic: push timeout / testing
Posted By: midnit
Subject: push timeout / testing
Date Posted: 20-Jan-2012 at 10:02am
Is there any way for the client to test if its still going to receieve pushes?
 
In our app the client needs to be able to receive for the life of the client which could be days long and be confident that it is still receiving the data its expecting. Timeouts and momentary losses of connectivity are a going to happen, so whats a good way to test for loss and reconnect in a timely manner.


Replies:
Posted By: smi-mark
Date Posted: 20-Jan-2012 at 11:01am
You should be able to use the EntityServerError event on the EntityManager to detect loss of connection

Posted By: midnit
Date Posted: 20-Jan-2012 at 11:08am
Spectacular! Thank you for the quick respond. I will check this out.

Posted By: midnit
Date Posted: 20-Jan-2012 at 12:09pm
Hmm, perhaps you meant general loss of connection as it does not give any error when a push is timed out or no longer responding.

Posted By: kimj
Date Posted: 20-Jan-2012 at 5:11pm
We haven't had great luck with WCF informing us when a connection has faulted, even less when it's a duplex push channel which can often be idle.  As you found, the push error won't be routed through the EntityServerError handler.  In theory, your callback handler will receive errors through the SubscriptionOperation.Error property, but it doesn't look as though a timeout or other communication error will make it through.   We do attempt auto-retry when we are able to detect a failure though. 
 
We'll take a look to see if there's something we can do here.


Print Page | Close Window