Volatility of exclusive collections

[ConvertFromOldNGs]

by Torrie >> Wed, 15 Feb 2006 4:42:12 GMT

How have people handled setting the volatility of exclusive collections? If a collection class is used for stable or frozen collections as well as volatile collections (sorted by the same keys,) then it seems like you need to either define volatile and stable or frozen collection classes or explicity set the volatility of the collections in code. I'm wondering whether it would be nice to be able to set this when defining an exclusive reference. Can anyone offer advice on this?

Does anyone know if an exclusive reference inherits the volatility from its owner?

Torrie

[ConvertFromOldNGs]

by allistar >> Wed, 15 Feb 2006 8:04:28 GMT

Once my clients upgrade to 6.1 my intention is to set the volatility on a collection instance basis in code rather than at a collection class level. Rarely would a collection class be used in the same volatility scenario across the entire system.

Defining volatility when defining exclusive references would be a handy feature.

Regards,
Allistar.