Reported by jasper, 18 months ago.

The wrappers for CapeRegistryWriter? and CapeRegistryKeyReader? add a reference too many to the constructed object, causing their memory not to be released (memory leak).

Code that uses these types (CapeRegistryWriter? and CapeRegistryKeyReader?) directly should be rebuilt against the new client headers. Most code would not use these types directly (but would use the Registrar types instead)

Reported by jasper, 18 months ago.

The definition of CapeWindowId? lacks the COBIA namespace.

Reported by jasper, 3 years ago.

COBIA based PMCs are made available to COM via COMBIA, which is currently done with the "Apartment" threading model, much along the line of most COM based CAPE-OPEN components. This threading model is more restrictive than it needs to be. The details of the COBIA threading model will be further refined in COBIA phase III, but the general concept is that it is ok for the PME to use the PMC from any thread, as long as it is not done concurrently. PMCs that do not support this threading model have the option to register as 'restricted threaded' which implies that the PME can access the PMC only from the thread in which it was created.

The COMBIA based COM registration for COBIA based PMC components is to be changed accordingly: if a PMC identifies itself as restricted threaded, the COMBIA threading model will be "Apartment". Otherwise it will be "Both" which closer agrees with the default COBIA threading model.