SystemUpdateID event

[CraigD]

There was a bug in my code - where I was not handling 'transfer-encoding: chunked', this is now fixed. The SUBSCRIBE message I send is

Code:

SUBSCRIBE /1bd3d9ee-6743-4412-9e71-07fa5c3b3199/upnp.org-ContentDirectory-1/event HTTP/1.1
CALLBACK: <http://192.168.0.8:42541/>
NT: upnp:event
TIMEOUT: Second-1800
Connection: close
Accept-Encoding: gzip, deflate
Accept-Language: en-GB,*
User-Agent: Mozilla/5.0
Host: 192.168.0.8:9791

MinimServer reponds with

Code:

HTTP/1.1 200 OK
SERVER: Posix/200809.0 UPnP/1.1 ohNet/1.0
SID: uuid:1bd3d9ee-6743-4412-9e71-07fa5c3b3199-4
TIMEOUT: Second-1800
Connection: close

I then immediately receive a notification:

Code:

NOTIFY / HTTP/1.1
Host: 192.168.0.8:9791
Content-Type: text/xml; charset="utf-8"
Nt: upnp:event
Nts: upnp:propchange
SID: uuid:1bd3d9ee-6743-4412-9e71-07fa5c3b3199-4
Transfer-Encoding: chunked
Seq: 0
Connection: close

<?xml version="1.0"?><e:propertyset xmlns:e="urn:schemas-upnp-org:event-1-0"><e:property><TransferIDs></TransferIDs></e:property><e:property><SystemUpdateID>52</SystemUpdateID></e:property><e:property><ContainerUpdateIDs></ContainerUpdateIDs></e:property></e:propertyset>

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?

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?