[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (WSDD-4) Remove dependency ondevice transport address from device metadata
[ http://tools.oasis-open.org/issues/browse/WSDD-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414#action_16414 ]
Antoine Mensch commented on WSDD-4:
-----------------------------------
Requested clarification: the above proposal defines a new relative addressing mechanism local to the DPWS Relationship WS-Mex dialect used to exchange metadata between DPWS devices and DPWS clients. Endpoints using the above syntax are not expected to appear anywhere else, so should not create confusion w.r.t. standard addressing mechanisms.
> Remove dependency on device transport address from device metadata
> ------------------------------------------------------------------
>
> Key: WSDD-4
> URL: http://tools.oasis-open.org/issues/browse/WSDD-4
> Project: OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) TC
> Issue Type: Improvement
> Components: DPWS Specification
> Environment: N/A
> Reporter: Antoine Mensch
> Assignee: Antoine Mensch
>
> 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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]