[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsia][wsrp-interfaces] Specific or general destroy mechanism (s)
Hi Gil. What API are you refering to? The general Win32 call to release handles is a generic CloseHandle no matter if it is a process handle, file handle, etc. Even the COM API has a generic Release call in the IUnknown interface. I prefer the generic mechanism to release handles. Conceptually it does not make any difference what type of handle/entity you release, so there is not need for specific method. In addition it makes algorithms like garbage collection, reference counters, etc much easier to implement as the can be implemented in a generic way. Best regards Carsten Leue ------- Dr. Carsten Leue Dept.8288, IBM Laboratory Böblingen , Germany Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401 |---------+----------------------------> | | Gil Tayar | | | <Gil.Tayar@webcol| | | lage.com> | | | | | | 07/23/2002 01:37 | | | PM | |---------+----------------------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| | | | To: wsrp-interfaces@lists.oasis-open.org, wsia@lists.oasis-open.org | | cc: | | Subject: RE: [wsia][wsrp-interfaces] Specific or general destroy mechanism (s) | | | | | >--------------------------------------------------------------------------------------------------------------------------------------------------| Well, MS tried the "general" approach in its Win16 API, and moved the "specific" way in its Win32 API. I can certainly understand it - I always prefer being specific. -----Original Message----- From: Rich Thompson [mailto:richt2@us.ibm.com] Sent: Mon, July 22, 2002 17:14 To: wsrp-interfaces@lists.oasis-open.org; wsia@lists.oasis-open.org Subject: [wsia][wsrp-interfaces] Specific or general destroy mechanism(s) The current draft spec has a generic release mechanism (releaseHandles()). At times more specific mechanisms have been mentioned (deregisterConsumer() & destroyEntities()). Advantages/disadvantages I see for the generic mechanism are: Advantages: - Single operation in the interface - Extensible ... can easily deal with new handle types as they are added to the spec. - Disadvantages: - Implies an inheritance relationship between handles. This isn't bad, but isn't required for specific mechanisms. - Type checking moved to the application level (this depends on how we specify the serialization of the handles). - Harder to explain as the operation is more abstract and therefore dependent on what is concretely passed. - Comments / thoughts / preferences? ---------------------------------------------------------------- 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