[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: No Subject
If we use HTTP on TCP/IP, we can get those information from those transport protocol, but WS-R spec should be used with other transport protocol also. And it is better to be consistent to identify a message sender and receiver regardless the underlying protocol. In my opinion, we have two choices: 1) We keep From and To element in WS-R specification until the standard spec for general header is standardized. 2) We create a separate specification for general header specification. From/To, Message identification element, and some other general elements can be defined in the specification. And WS-R spec refers to the specification. And I feel the option 1) above might be better for now, since we have limited time for the spec finalization. We may want to use general header spec with the next version(2.0?) of RM spec, but not with this version(1.1?). Thanks, Iwasa -- Hi all, Sorry, I was not enough clear here. As you see from the other mail I sent, my opinion is, that we should consider, what elements beyond the reliable messaging we define, especially the From/To elements are not needed. Not only because they don't give more information, but are not enough for routing either (which is out of scope furthermore). This requirement in my understanding is a spec. issue and during the specification we should consider, what to keep from the input specification. br, Magdolna -----Original Message----- From: ext [mailto:magdolna.gerendai@nokia.com] Sent: June 25,2003 17:37 To: marc.andrue.goodner@sap.com; wsrm@lists.oasis-open.org Subject: RE: [wsrm] REL-13 proposal Hi Marc, I think, we should keep this spec. requirement. The "From/To" elements are not enough for routing alone. br, Magdolna -----Original Message----- From: ext Goodner, Marc Andrue [mailto:marc.andrue.goodner@sap.com] Sent: June 18,2003 13:25 To: wsrm@lists.oasis-open.org Subject: [wsrm] REL-13 proposal Proposal: Close with no action. Rational is that we should pay careful attention to this issue as we determine which elements should be required/optional and what their fault characteristics are, but there is nothing we can reflect in the specification directly for this issue. Regards, Marc g Issue REL-13 Title: Use of elements beyond WSRM Description: The existing specification contains a number of elements that may apply to many use cases beyond reliable messaging. For example, From / To may be useful for (unreliable) routing through an intermediary. Alignment on a set of common components meeting these general requirements across use cases should be sought. You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]