[OASIS Issue Tracker] Updated: (WSDD-6) DPWS - WS-Eventing does notwork when subscriber is not addressable

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/WSDD-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Toby Nixon updated WSDD-6:
--------------------------

    Summary: DPWS - WS-Eventing does not work when subscriber is not addressable  (was: DPWS - WS-Eventing does not work when subscriber in not addressable)

Changed "in" to "is" in the Summary.

> DPWS - WS-Eventing does not work when subscriber is not addressable
> -------------------------------------------------------------------
>
>                 Key: WSDD-6
>                 URL: http://tools.oasis-open.org/issues/browse/WSDD-6
>             Project: OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) TC
>          Issue Type: Bug
>          Components:  DPWS Specification
>         Environment: N/A
>            Reporter: Antoine Mensch
>            Assignee: Antoine Mensch
>
> The current WS-Eventing mechanism selected by DPWS is based on a push mechanism which requires the event source to connect to the subscriber to deliver the event notification. This creates problems in to very common cases: (i) when the subscriber is behind a firewall using NAT; (ii) when the subscriber is a Web application (e.g. Ajax or Java, Flash or Silverlight applets) which cannot accept incoming connections.

-- 
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