New Posts New Posts RSS Feed: push timeout / testing
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

push timeout / testing

 Post Reply Post Reply
Author
midnit View Drop Down
Senior Member
Senior Member
Avatar

Joined: 22-Jun-2009
Location: Charlotte
Posts: 112
Post Options Post Options   Quote midnit Quote  Post ReplyReply Direct Link To This Post Topic: push timeout / testing
    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.
Back to Top
smi-mark View Drop Down
DevForce MVP
DevForce MVP
Avatar

Joined: 24-Feb-2009
Location: Dallas, Texas
Posts: 343
Post Options Post Options   Quote smi-mark Quote  Post ReplyReply Direct Link To This Post Posted: 20-Jan-2012 at 11:01am
You should be able to use the EntityServerError event on the EntityManager to detect loss of connection
Back to Top
midnit View Drop Down
Senior Member
Senior Member
Avatar

Joined: 22-Jun-2009
Location: Charlotte
Posts: 112
Post Options Post Options   Quote midnit Quote  Post ReplyReply Direct Link To This Post Posted: 20-Jan-2012 at 11:08am
Spectacular! Thank you for the quick respond. I will check this out.
Back to Top
midnit View Drop Down
Senior Member
Senior Member
Avatar

Joined: 22-Jun-2009
Location: Charlotte
Posts: 112
Post Options Post Options   Quote midnit Quote  Post ReplyReply Direct Link To This Post 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.
Back to Top
kimj View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 09-May-2007
Posts: 1391
Post Options Post Options   Quote kimj Quote  Post ReplyReply Direct Link To This Post 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.
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down