W3C home > Mailing lists > Public > public-ws-addressing@w3.org > June 2005

RE: Why is [message id] required for requests but not for other messages?

From: Yalcinalp, Umit <umit.yalcinalp@sap.com>
Date: Tue, 14 Jun 2005 01:07:05 +0200
Message-ID: <2BA6015847F82645A9BB31C7F9D6416510652E@uspale20.pal.sap.corp>
To: "David Hull" <dmh@tibco.com>, <public-ws-addressing@w3.org>

 

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

--umit
Received on Monday, 13 June 2005 23:07:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:05 GMT