discovery-api/Overview.src.html
changeset 332 e19dc529aacc
parent 331 43b139afeba9
child 371 8b03e17da083
     1.1 --- a/discovery-api/Overview.src.html	Thu Jan 17 15:07:19 2013 +0100
     1.2 +++ b/discovery-api/Overview.src.html	Thu Jan 17 15:08:37 2013 +0100
     1.3 @@ -1477,31 +1477,31 @@
     1.4          </p>
     1.5          <p>
     1.6            Let <var>dial version</var> be the version number specified in the <a>valid service type</a> token.
     1.7 -          Let <var>dial search target</var> be the concatentation of the 
     1.8 +          Let <var>dial search target</var> be the concatentation of the
     1.9            <code>urn:dial-multiscreen-org:service:dial:</code> string constant with the <var>dial version</var>
    1.10 -          (currently, <var>dial version</var> can only be <code>1</code>) 
    1.11 +          (currently, <var>dial version</var> can only be <code>1</code>)
    1.12          </p>
    1.13          <p>
    1.14            The user agent MUST issue all <a title="search request for DIAL devices">search requests for DIAL
    1.15            devices</a> with a HTTP request line equal to <code>M-SEARCH * HTTP/1.1</code>, with a HOST header equal to
    1.16            the reserved multicast address and port of <code>239.255.255.250:1900</code>, a MAN header equal to
    1.17            <code>ssdp:discover</code>, an ST header equal to <var>dial search target</var>
    1.18 -          and a user-agent defined MX header equal to a <dfn>maximum UPnP advertisement response wait time</dfn>
    1.19 +          and a user-agent defined MX header equal to a <dfn>maximum DIAL advertisement response wait time</dfn>
    1.20            value between <code>1</code> and <code>5</code> seconds.
    1.21          </p>
    1.22          <p>
    1.23            The user agent MUST listen for any incoming responses to a <a>search request for DIAL devices</a>.
    1.24          </p>
    1.25          <p>
    1.26 -          For each <dfn>HTTP Response</dfn> following an initial <a>search request for DIAL devices</a> sent on a
    1.27 +          For each HTTP Response following an initial <a>search request for DIAL devices</a> sent on a
    1.28            <a>standard UPnP address and port</a> the user agent MUST run the following steps:
    1.29          </p>
    1.30          <ol class="rule">
    1.31 -          <li>If the <a>HTTP Response</a> is not a HTTP 200 OK response then this response is invalid and the user
    1.32 +          <li>If the HTTP Response is not a HTTP 200 OK response then this response is invalid and the user
    1.33            agent MUST discard this response, abort any remaining steps and return. The user agent MAY issue a new
    1.34            <a>search request for DIAL devices</a> as a result of this error occurring.
    1.35            </li>
    1.36 -          <li>If the <a>maximum UPnP advertisement response wait time</a> has been exceeded since the initial <a>search
    1.37 +          <li>If the <a>maximum DIAL advertisement response wait time</a> has been exceeded since the initial <a>search
    1.38            request for DIAL devices</a> was sent then the <a>HTTP Response</a> is invalid and the user agent MUST
    1.39            discard this response, abort any remaining steps and return. The user agent MAY stop listening for responses
    1.40            from the current <a>search request for DIAL devices</a> as a result of this error occurring. Equally,
    1.41 @@ -1526,7 +1526,7 @@
    1.42            </li>
    1.43          </ol>
    1.44          <p>
    1.45 -          The rule for <dfn>obtaining a UPnP Device Description File</dfn> is the process of obtaining the contents of
    1.46 +          The rule for <dfn>obtaining a DIAL Device Description File</dfn> is the process of obtaining the contents of
    1.47            a standard UPnP Device Description [[!UPNP-DEVICEARCH11]] from a URL-based resource. This rule takes three
    1.48            arguments - <var>device descriptor URL</var>, <var>device identifier</var> and <var>device expiry</var> - and
    1.49            when called the user agent MUST run the following steps: