[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsrp-wsia] [I#106] Uniqueness of entityHandles
How does the consumer know that the handle is not unique? Else the consumer would have to add the GUID (large random number) on each cloneEntity() result handle. -----Original Message----- From: Tamari, Yossi [mailto:yossi.tamari@sap.com] Sent: 09 October 2002 12:00 To: wsrp-wsia@lists.oasis-open.org Subject: RE: [wsrp-wsia] [I#106] Uniqueness of entityHandles Or the consumer could attach a GUID to the returned handle and then remove it before sending the handle back to the producer. Why put the load of making the life of a specific consumer implementation on every producer? Yossi. -----Original Message----- From: Andre Kramer [mailto:andre.kramer@eu.citrix.com] Sent: Wednesday, October 09, 2002 11:29 AM To: wsrp-wsia@lists.oasis-open.org Subject: RE: [wsrp-wsia] [I#106] Uniqueness of entityHandles This could get very confusing for consumers as they should be allowed to test for equality by comparing handles? For your example, the producer could append a large random number (impacting handle size) on clone and strip it off when receiving the handle back to make handles appear unique. regards, Andre -----Original Message----- From: Tamari, Yossi [mailto:yossi.tamari@sap.com] Sent: 09 October 2002 10:15 To: wsrp-wsia@lists.oasis-open.org Subject: RE: [wsrp-wsia] [I#106] Uniqueness of entityHandles While Gil is obviously correct in theory, it might useful in practice to allow a producer to return the same handle as a result of CloneEntity. If this entity has no persistence, there doesn't seem to be a need for a different handle, and it removes the need for this simple producer of dealing with multiple entityHandles. Yossi. -----Original Message----- From: Gil Tayar [mailto:Gil.Tayar@webcollage.com] Sent: Wednesday, October 09, 2002 6:41 AM To: wsrp-wsia@lists.oasis-open.org Subject: RE: [wsrp-wsia] [I#106] Uniqueness of entityHandles How can it be other than a MUST? If two entities have the same handle, then they are, by definition, the same entity. This is not even a MUST - it is evident by the very nature of the definition of a handle as a unique identifier of something. -----Original Message----- From: Gil Tayar [mailto:Gil.Tayar@webcollage.com] Sent: Wed, October 09, 2002 06:38 To: wsrp-wsia@lists.oasis-open.org Subject: [wsrp-wsia] [I#106] Uniqueness of entityHandles Topic: Interface Class: Technical Raised by: Rich Thompson Title: Uniqueness of entityHandles Date Added: 9-Oct-2002 Document Section: Interfaces/6 Description: Do we want a statement about uniqueness of entity handles within the scope of a registration? Would it be a SHOULD or a MUST? ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl> ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl> ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl> ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl> ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC