RE: Issue 040 - DPWS - Use standard Request/Reply MEP in directedprobe

[Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>]

Ignore this issue thread.

Issue number 40 is already taken by "Issue 040 - DPWS - PresentationURL in ThisDevice instead of ThisModel metadata".

I will assign a separate number for this issue "DPWS - Use standard Request/Reply MEP in directed probe". Thanks.

-----Original Message-----
From: Ram Jeyaraman
Sent: Wednesday, September 17, 2008 11:32 AM
To: 'ws-dd@lists.oasis-open.org'
Subject: Issue 040 - DPWS - Use standard Request/Reply MEP in directed probe

This issue is assigned the number 040. For further discussions on this issue, please refer to this issue number or use this thread.

-----Original Message-----
From: Antoine Mensch [mailto:antoine.mensch@odonata.fr]
Sent: Tuesday, September 16, 2008 4:00 PM
To: Ram Jeyaraman
Subject: NEW Issue - Use standard Request/Reply MEP in directed probe

Please defer discussions on this issue until a time this issue is
accepted and is assigned a number.

Document: DPWS
Location (defaults to line number): 334
Owner: Antoine Mensch

Description:
R1022 is a translation over the HTTP protocol of the expected behavior
of a device when using WS-Discovery over UDP (namely, no response is
expected from a device that does not match the probe). However, this
introduces a MEP (in/optional out) which is not generally supported by
existing Web Services stacks (they usually support only one-way and
request/reply MEPs). This makes the use of the directed probe mechanisms
not always easy to implement in some clients.

Proposed resolution:
For the sake of interoperability, it might be better to allow an empty
ProbeMatches element as a response for a non-matching directed probe.