Hi Marc,
You're right. That was kind of an annoying e-mail. Sorry. And I'll try
never to say "pattern" again, LOL. Still friends? :-)
By the way, if anyone is interested in finding out what the heck I
was talking about, the origins of the serialization cache key in
Jonathan Weedon's work is r
Well,
scott wrote to me "it's not worth arguing about" and I sort of agree,
but for the sake of completeness, at least on my part, here goes
|This thread is a little funny to me. We got the idea of a cache key
|from a thread on ejb-interest, where Jonathan Wheedon (Borland's
|very intelligent a
This thread is a little funny to me. We got the idea of a cache key
from a thread on ejb-interest, where Jonathan Wheedon (Borland's
very intelligent alien...their Rickard, so to speak) described how it
was implemented in IAS. But if memory serves me, the trigger for
the thread was how the fat
ok,
scott has put his finger on a solid fact, you can screw up your PK and the
cache key won't save you. It is not what I thought.
I think the point he makes is that even though the PK hashcode and equals
are really easy to screw up at least it is your responsibility as per the
spec.
Frankly w
