SystemUpdateID event

[simoncn]

(05-05-2016 21:33)CraigD Wrote:  However, If I now create a new playlist then call 'rescan' in 'startc' - no notification is sent. Are notifications only sent on the initial subscribe?

No, they are sent whenever the SystemUpdateID property changes and the subscription is still active.

Quote:There seems to be an issue with my code - where I'm not seeing the 'bybye' and 'alive' messages. (Maybe because I'm running on the same host). Is it expected that after a rescan minim will send a 'byebye', a client should disconnect (unsubscribe), minim restarts and sends an 'ssdp:alive', then the client re-subscribes - and gets the new UpdateID this way?

Your understanding is correct. The 'rescan' command causes the MediaServer device to be destroyed and recreated. When the device is destroyed, MinimServer sends a byebye notification and the subscription is terminated. The control point must establish a new subscription after the MediaServer device has been recreated and has sent an alive notification. When it does this, it will receive a notification containing the current value of SystemUpdateID.

This sequence of events should happen whether or not the control point is running on the same host as the server. However, if the control point and server are running on the same host, you will not be able to use Wireshark to see messages exchanged between the server and the control point. Instead, you can see these messages by setting the MinimServer property ohnet.debug to All-Timer and setting the MinimServer logging level to Debug. The messages can be seen by looking in the minimserver.log file (not the log window).