[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Issue 125 - WS-Discovery - Finding services require a doubleroundtrip
Here’s a proposed resolution to Issue 125. I
think the previously proposed changes to
Section 3.1 are fine. The concern I expressed on the last teleconference was with the
proposed change to Section 5.3, and was that the
new sentence (“If a Target Service has transport address(es), at least
one MUST be included to avoid an immediate Resolve.”) is ambiguous; it can be interpreted to mean that the target
service need only include one transport address in its ProbeMatch but
could include more at its option. The intent as expressed on the last
teleconference was that the target service must include the same transport address(es) in its ProbeMatch that it would include in a
ResolveMatch if one were immediately requested. I therefore propose that the
text previously proposed be changed to the
following (all of the text is red because this is actually new text in 5.3,
even though some of it was copied from section 4.1): Section 5.3 /s:Envelope/s:Body/d:ProbeMatches/d:ProbeMatch/d:XAddrs
Transport
address(es) that MAY be used to communicate with the Target Service (or
Discovery Proxy). Contained URIs MUST NOT contain white space. In order to
avoid the need for the Client to immediately send a Resolve to obtain the
transport addresses of the Target Service, if a Target Service has one or more
transport addresses, XAddrs MUST be included in ProbeMatch, and the transport
addresses included in ProbeMatch MUST be the same as would be returned in a
ResolveMatch to the same Client. Note that the last sentence previously proposed is not included (“In
a managed mode, ALL transport address(es) SHOULD be included.”). It had
been cut and pasted from the description of the Hello message in Section 4.1,
which made sense because Section 4.1 was referenced in the previous definition.
However, it doesn’t actually make sense in the case of ProbeMatch, which is
sent only to clients and not to proxies, so the requirement to include all
transport addresses does not apply. It only makes sense to send all transport
addresses when a Target Services is sending a Hello in managed mode to a proxy,
so that the proxy has full information and is able to send the appropriate
information on behalf of the service when a Client sends a Probe to the proxy.
We may want to consider also making this same clarification in the description
of the XAddrs element of ResolveMatch.
-- Toby Toby Nixon
| Senior Standards Program Manager | Windows Device and
Storage Technologies | Microsoft Corporation toby.nixon@microsoft.com
| www.microsoft.com
| V: +1 425 706 2792 | M: +1 206 790 6377 | F: +1 425
708 4811 Subject: Issue 125 - WS-Discovery - Finding services require a
double roundtrip
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]