#22 Bug in sending advertisment set

[jay]

In section 7.2.4.3 - UPnP devices send each
advertisment set's HTTP Message several(NUM_COPY)
times. So, the main and doubled advertisment sets'
messages were taken as a different service.
I deleted NUM_COPY times sending in function
NewRequestHandler.
I think the bug was there.

[jay]

Logged In: YES
user_id=1499411

here is patch for the changes

[jay]

patch for sending advertisment set

[jay]

Logged In: YES
user_id=1499411

Real PATCH patch for the changes

[jay]

Logged In: YES
user_id=1499411

According to Hypertext Transfer Protocol HTTP 1/1:
Section 1.1.2 Discovery: Advertisement: Device available
-- NOTIFY with ssdp:alive

"NT" in NOTIFY message described the next:
NT
Required header defined by GENA. Notification Type.
Must be one of the following. (cf. table above.) Single
URI.
upnp:rootdevice
Sent once for root device.
uuid:device-UUID
Sent once for each device, root or embedded.
Device UUID specified by UPnP vendor.
urn:schemas-upnp-org:device:deviceType:v
Sent once for each device, root or embedded.
Device type and version defined by UPnP Forum working
committee.
urn:schemas-upnp-org:service:serviceType:v
Sent once for each service.
Service type and version defined by UPnP Forum working
committee.

Because of 'while(NUM_COPY)' in the function
'NewRequestHandler' NOTIFY messages with the same values of
'upnp:rootdevice', 'uuid:device-UUID',
'urn:schemas-upnp-org:device:deviceType:v',
'urn:schemas-upnp-org:service:serviceType:v' are sent more
than ones.

[jay]

Logged In: YES
user_id=1499411

According to UPnP Device Architecture, but not that protocol