From: Gerd M. <ge...@sm...> - 2001-07-09 09:13:21
|
On Mon, 9 Jul 2001 09:37:35 +0100 "Kal Ahmed" <ka...@te...> wrote: > Hi Gerd, > > I don't know how I managed to miss this message ... sorry for the delay in > replying. > > I think that using a hashmap internally for Topic.rolesPlayed and > Member.player attributes might be a useful thing to do, and as you note, it > would enable a more convenient removeXXX() operation. However, it should be > noted that from an XTM spec point of view, this would not be sufficient to > meet the requirements to suppress duplicate players of roles in an > association. Also, I wonder about the time and space overhead of the use of > a HashMap in the in-memory implementation when the index would really only > be used for removals. Maybe you are right, since removals don't happen that often. > So my position would be +1 to adding the suggested operations to the > interface but -1 on using a HashMap for the in-memory implementation (I > don't yet know enough about Ozone internals to determine the best course of > action for that implementation). Okay, +1 for adding the removeXXX() methods to the interface. Best Regards, Gerd -- ________________________________________________________________ Gerd Mueller ge...@sm... SMB GmbH http://www.smb-tec.com |