OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-dd message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Issue 017 - Support relative URLs for hosted services


This issue is assigned the number 017. 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 3:50 PM
To: Ram Jeyaraman
Subject: NEW Issue - Support relative URLs for hosted services

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): 250
Owner: Antoine Mensch

Description:
R0042 limits supported hosted services addresses to HTTP transport
addresses (presumably absolute). As hosted services generally share the
network addresses (ip ddress + port) of their hosting device, allowing
relative addresses (as done for the presentationURL field) could reduce
the need to duplicate endpoint references for hosted services for all
the transport addresses of their hosting device. It could also help
simplify the management of metadata when multiple network interfaces are
used, by allowing the hosting metadata to remain constant across network
interfaces. This issue has appeared when a new version of the DPWS spec
has changed hosted service addresses for logical to HTTP transport. Note
also that there is an inconsistency in the management of metadata: the
transport addresses of devices are not covered by the metadata version,
while the transport addresses of hosted services are (see R2030).

Proposed resolution:
Allow hosted services to use relative URLs.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]