[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Issue 122 - WS-Discovery - Remove special "ad-hoc" scope
Please ignore this thread. I will reassign this to a new issue
123. Thanks. From: Ram Jeyaraman
[mailto:Ram.Jeyaraman@microsoft.com] This issue is assigned the number 122. For further
discussions on this issue, please refer to this issue number or use this
thread. From: Vipul Modi Spec: WS-Discovery Version: Working Draft 04 Details: Section 4.1 Hello specifies that if a service does not have
a Scope it is said to be in an “adhoc” scope http://docs.oasis-open.org/ws-dd/discovery/2008/09/adhoc. The absence of the Scopes in the Hello may not mean that a
Target Service does not have any scopes. The Target Service may not advertise
the scopes because of the security reason or because of the size limitation. In
such case it is difficult for the client to assume that service is in an
“ad-hoc” scope. What happens when the Probe include this special value, should
all services that advertised empty Scopes respond or should the services that
do not have any scopes configured respond? Furthermore there does not appear to
be any scenario for this special treatment for the empty Scopes field. It is
seems to be an unused feature that is not well understood and defined. Proposal: Remove the special “ad-hoc” scope. Section 4.1 /s:Envelope/s:Body/*/d:Scopes Unordered set of Scopes the Target
Service (or Discovery Proxy) is in, which MAY be of more than one URI scheme.
If included, MUST be a set of absolute URIs, and contained URIs MUST NOT
contain white space. If omitted or empty no implied
value In a managed mode, all Scopes
SHOULD be included. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]