isn't necessary...
make the mimetype function work..
do the notifies as part of startService which will get called once
the protocol is up...
[git-p4: depot-paths = "//depot/": change = 1277]
setup immediately.. This does mean we have to queue up packets...
This means our caller doesn't have to know about SSDP_ADDR anymore...
Though we should still provide a function to start us up..
[git-p4: depot-paths = "//depot/": change = 1270]
sometime between .5 and 1 seconds, and the second is between 1 and
5 seconds later...
Also, schedule a resend of the notify for sometime between a third
and a half of the max-age of it all...
send out two byebye notifications just incase...
Yes, this increases traffic, but it's required per the spec.. and
w/ 100Mbit it's not too big of a deal..
[git-p4: depot-paths = "//depot/": change = 1088]
This should prevent the DSM-520 from saying we've disappeared...
7 minutes means 4 sends before the 30 minutes max-age hits and is
a pretty good compromise, though we do send out five notifies each
time...
[git-p4: depot-paths = "//depot/": change = 1087]
notifications when we register an address...
make it so we send our responses on our own ip, and not the
multicast, along with turning off multicast loopback so we
don't see our own traffic...
Move the registering the SSDP services after the start of the
http server since we now send out notifications...
[git-p4: depot-paths = "//depot/": change = 718]