Subject: [DISCUSS] changes to registerInterest API


Does anyone actually do this in practice?  If so, yikes!

Even if the List is immutable, the elements may not be, so using a List as
a key starts to open 1 up to a lot of problems.

As others have pointed out in SO and other channels, information should not
be kept in the key.

It is perfect fine to have a "Composite" Key, but then define a CompositeKey
class type with properly implemented equals(:Object) and hashCode():int
methods.

For the most part, Keys should really only ever be simple Scalar values
(e.g. Long, String, etc).

-j
On Thu, Nov 30, 2017 at 2:25 PM, Jason Huynh <[EMAIL PROTECTED]> wrote:

-John
john.blum10101 (skype)