Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Error handling for sync invocations in Java
09-12-2011, 01:54 PM
Post: #29
RE: Error handling for sync invocations in Java
(09-12-2011 11:43 AM)simonc Wrote:  I've fixed this now so the updates should hopefully appear on github this evening.

Thanks!

Quote:In theory, this seemed like a no brainer. In practice however, its not so straightforward. Asset and some versions of twonky are capable of sending out multiple announcements for different addresses, all of which are valid. ohNet reacts to this by running Removed/Added messages each time an announcement is received.

I still tend to think that ohNet's behaviour is reasonable but we'll have to see how disruptive it proves...


Does this mean that if Asset sends out two announcements for address A and then for address B, ohNet will run the following callbacks:
deviceAdded(A)
deviceRemoved(A)
deviceAdded(B)

If so, this seems to be misleading from the control point's perspective because it appears that A has gone away, which isn't the case. Or would ohNet do the following:
deviceAdded(A)
deviceRemoved(A)
deviceAdded(A)
deviceAdded(B)

This is also likely to be confusing/disruptive for the control point if it is currently communicating with the device using address A.
Find all posts by this user


Messages In This Thread
RE: Error handling for sync invocations in Java - simoncn - 09-12-2011 01:54 PM

Forum Jump: