- From: Tom Rutt <tom@coastin.com>
- Date: Mon, 13 Jun 2005 19:20:50 -0400
- To: "Yalcinalp, Umit" <umit.yalcinalp@sap.com>
- CC: David Hull <dmh@tibco.com>, public-ws-addressing@w3.org
check my concern below umit's comment Yalcinalp, Umit wrote: > > > > >>-----Original Message----- >>From: public-ws-addressing-request@w3.org >>[mailto:public-ws-addressing-request@w3.org] On Behalf Of David Hull >>Sent: Monday, Jun 13, 2005 3:07 PM >>To: public-ws-addressing@w3.org >>Subject: Why is [message id] required for requests but not >>for other messages? >> >> >>If [message id] is to be leveraged for uses other than correlation, >>particularly duplicate elimination and security, wouldn't those >>considerations apply at least equally well to non request/reply >>interactions? If not, what is the basis for requiring >>[message id] for >>requests but not for other types of message? >> >> >> >> >> > >Well, if you recall from the f2f, we wanted to require message id across >the board :-) > > > but those semantics are not there in the present document, MesssageId is only required when correlation of a reply is required. Tom Rutt >--umit > > > -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@us.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133
Received on Monday, 13 June 2005 23:23:13 UTC