W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > March 2009

RE: [Bug 6692] New: Remove Mode from the specification

From: Geoff Bullen <Geoff.Bullen@microsoft.com>
Date: Mon, 16 Mar 2009 22:13:53 -0700
To: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Message-ID: <5AAAA6322448AA41840FC4563A30D6E8439A06FB6A@NA-EXMSG-C122.redmond.corp.microsoft.com>
Issue 6692 - WS-Eventing: Remove Mode from the specification
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6692

It seems the intent here is to remove the "mode" element from the specification.  The main reason behind this seems to be that the WG can't think of any reason to have it.  Mode seems to refer to "transport" kinds of concepts - how things are delivered, whereas Format refers to the format of what is delivered.  This makes sense.  So the question is, do we need to be able to specify transport concepts in Eventing, or do they all just compose in nicely?

The issue description mentions that complex queuing and distribution can be supported without Mode, as can MakeConnection.  In terms of MakeConnection, we should specifically talk about that as part of issue 6432.  Certainly we cannot close on this issue before we close on 6432.

As for the general need for a Mode, it is not clear to me at all that other specs will just compose nicely on top of Eventing and work without having to specify anything specific about them to the Eventing Environment.  Exactly how do you propose that a queuing system will interact with Eventing?  How would a multicast solution work?  Can you provide a basic example of how you would imagine both of these scenarios would compose (without using Mode)?

We believe that both of these (and also MakeConnection) will require some knowledge and configuration during the Subscribe Request, and if that is true, then the Mode element is the right place for those extensions to be placed.

--Geoff

-----Original Message-----
From: public-ws-resource-access-notifications-request@w3.org [mailto:public-ws-resource-access-notifications-request@w3.org] On Behalf Of bugzilla@wiggum.w3.org
Sent: Thursday, March 12, 2009 8:37 AM
To: public-ws-resource-access-notifications@w3.org
Subject: [Bug 6692] New: Remove Mode from the specification

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6692

           Summary: Remove Mode from the specification
           Product: WS-Resource Access
           Version: CR
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: Eventing
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: david.Snelling@UK.Fujitsu.com
         QAContact: public-ws-resource-access-notifications@w3.org


The concept of Mode is redundant in the current version of the specification.
All events can be thought of as being delivered. There is no actual definition
of "Push Mode" and no other recommended modes. We even have a MakeConnection
strategy to allow clients behind NATs to fetch events. Likewise, strategies for
complex queuing and distribution are supportable without adding additional
modes and are outside the scope of this specification.

Proposal: Remove /s:Envelope/s:Body/*/wse:Delivery/@Mode from the specification
and all references to Push Mode. A simple explanation of the delivery idea and
a pointer to some of the techniques available will be needed.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Received on Tuesday, 17 March 2009 05:14:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:17:51 GMT