The control app thread

[simoncn]

From the recent posts I have seen about this, this LUMIN app bug appears to affect renderer connections rather than server connections.

This indicates there is a bug in how the LUMIN app maintains UPnP connections/subscriptions with renderers. The LUMIN renderer works around this bug by sending frequent alive messages and so avoids being affected by this bug. Other renderers that correctly implement the UPnP specifications are affected by the bug unless they are proxied by BubbleUPnP Server with the special setting enabled.

This "ripple effect" is a great illustration of the problems caused when one component of a standards-based ecosystem fails to implement the required standard protocol correctly.

I hope the LUMIN app developers will fix this bug before other renderers are forced to also implement this incorrect behaviour for interoperability reasons.