The control app thread

[simbun]

(25-02-2023 19:31)bubbleguuum Wrote:  The blastAliveInterval option if BubbleUPnP Server is really for use as a last measure and band-aid when nothing else works to fix a renderer or media server discovery issue.
It is quite heavy handed, triggering SSDP traffic at regular interval which will be received by all UPnP control points on the network listening for such traffic and maybe other UPnP devices that are not interested in it but will have to process it anyway (to finally discard it).
So I would advise to use it with caution and to set the interval at the highest value possible that fixes the problem.

Now I'll preface this with, a little knowledge is a dangerous thing!

We appreciate the caution on the use of this setting, but given the BubbleUPnP documentation gives no idea of what an "average" ssdp:alive interval would normally be (if there is such a thing) does the following make sense?

It appears that a few devices on my network - including MinimServer - have a CACHE-CONTROL max-age of 1800 (I can't seem to find a standard for this stated anywhere though), and the spec states to re-send it at "at a randomly-distributed interval of less than one-half of the advertisement expiration time, so as to provide the opportunity for recovery from lost advertisements before the advertisement expires", would starting blastAliveInterval at 850, then lowering as necessary be a sensible approach?
Just don't want someone starting at 30 then incrementing by 10 every day for months on end :-)