W3C home > Mailing lists > Public > xmlp-comments@w3.org > February 2002

Re: UUID message identifiers

From: <noah_mendelsohn@us.ibm.com>
Date: Wed, 13 Feb 2002 11:57:31 -0500
To: Richard@Monson-Haefel.com
Cc: xmlp-comments@w3.org
Message-ID: <OF7BFA29BC.0A64E93E-ON85256B5F.00588970@lotus.com>
Speaking for myself, not the WG:  UUIDs are indeed useful, but there are 
also logistical issues involved in their generation.  One can imagine e.g. 
small devices in which it would be inconvenient.  SOAP makes it easy to 
layer functions into headers.  Nothing in SOAP prevents very widespread 
adoption of a header used to carry such UUIDs.  Nothing prevents a broad 
range of SOAP applications from using and mandating support for that 
header.  By keeping SOAP modular, we somewhat lower the bar on 
implementation requirements.  Also, we allow applications to leverage ID 
schemes that may be more natural in a particular environment.   So, it's a 

Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142


Richard Monson-Haefel <Richard@Monson-Haefel.com>
Sent by: xmlp-comments-request@w3.org
02/12/2002 09:36 AM
Please respond to Richard

        To:     xmlp-comments@w3.org
        Subject:        UUID message identifiers

It would be useful if SOAP messages were assigned a UUID when generated
by the initial sender. Has this been considered and if so, why has it
not been addressed in SOAP version 1.2 (draft 17)?



Richard Monson-Haefel
Author of Java Web Service (Titan Books 2002)
Author of Enterprise JavaBeans, 3rd Edition  (O'Reilly 2001)
Co-Author of Java Message Service (O'Reilly 2000)
Received on Wednesday, 13 February 2002 12:11:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:14:12 UTC