RE: [gupnp] [PATCH] Respond to M-SEARCH requests for urns specifying an eligible version



On Mon, 2010-07-12 at 22:29 -0400, Stephen Depooter wrote:
> If I have a device that implements versions 1, 2, and 3 of Media
> Server, and as per section 2.3 of the spec, includes and declares
> version 3 as the "highest supported version" of the MediaServer device
> type, then only the versions 1, 2, and 3 of MediaServer are supported.
> Clearly the device must respond to any search request for a
> MediaServer on the network when the request is for a supported
> version.  Since by definition version 4, 5 and 6 have new
> functionality compared to versions 1,2 or 3, then they are not
> supported.  Thus any request for a version 4, 5, or 6 is not supported
> and should not be responded to.  Since the control point that is dong
> the searches receives no responses, it MAY fall back and search for a
> lower version if it is behaving according to the details of the 1.3.2
> section of the spec.  Clearly the expectation is that if a control
> point is requesting a version of a device that is not supported it
> will not get flooded by irrelevant responses by every device that
> happens to implement only lower versions of the spec.

Sounds totally plausible to me and I also understand the specifications
that way. Zeeshan, I understand that you want to be pointed to a
document that clearly describes this behavior, without any room for
interpretation. But can you point out how this behavior could be
problematic or can you point us to parts of the specification that don't
agree with this interpretation? Otherwise I would suggest that the
patches are accepted. If they should really turn out to be problematic
in real life, then we can always revert that change.


Greetings,
Sven


-- 
Sven Neumann
Head of Software Development

RAUMFELD GmbH | Reichenberger Str. 124 | 10999 Berlin | Germany
Tel: +49.30.340.60.98.0 | Fax: +49.30.340.60.98.99 | s neumann raumfeld com

--
To unsubscribe send a mail to gupnp+unsubscribe\@o-hand.com



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]