Re: [ws-dd] DPWS and Eventing (Issues 052 and 056)

[Doug Davis <dug@us.ibm.com>]

Dan, Shin,
  In looking at these proposals,
am I correct in assuming that the base problem is the volume of events
being generated and the lack of a way for a subscriber to indicate which
level of granularity they want?  For example... one subscriber may
want all "printer events", but another may want just "printer
job status" events, while yet another may want just "printer
job status events for job id# 123" ?  And doing this filtering
over the soap body is expensive (ie. xpath) and potentially hard to manage
because the event data could vary even if the type of event remains the
same?

thanks
-Doug
______________________________________________________
STSM  |  Web Services Architect  |  IBM Software Group
(919) 254-6905  |  IBM T/L 444-6905  |  dug@us.ibm.com

Dan Driscoll <Dan.Driscoll@microsoft.com>

12/23/2008 01:11 PM

To	"ws-dd@lists.oasis-open.org" <ws-dd@lists.oasis-open.org>
cc
Subject	[ws-dd] DPWS and Eventing (Issues 052 and 056)

Hello all-
I took an AI to assemble some solutions
to the problem of the Action filter being insufficient for some applications
of DPWS and WS-Eventing.  This set of solutions incorporates the suggestions
from Ohtake-san, and a suggestion from Elmar Zeeb.
 
The goal of this document is to illustrate
the different ways WSDL authors can make use of the tools in WS-Eventing.
 
Several of these suggestions are similar,
but there are at least six different ways that spec authors can work around
the limitations in the Action filter.
 
Thanks
--D[attachment "DPWS Eventing.docx"
deleted by Doug Davis/Raleigh/IBM] ---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php