Yes, this change has been in since the start of 2.4, and people have complained about CacheKey showing up as a bottleneck since its release. It started showing up even more dramtically in the pending 2.4.4 codebase due to some other change that is banging on its ctor.
----- Original Message ----- From: "Bill Burke" <[EMAIL PROTECTED]> To: Sourceforge. Net" <[EMAIL PROTECTED]> Sent: Wednesday, November 14, 2001 6:06 AM Subject: RE: [JBoss-dev] CacheKey copy semantics and speed > Sorry to chime in so late....But hasn't my CacheKey change been in since > 2.4.0? > > Also remember why I added the copying to the CacheKey in the first place. > What I was doing in my application code was reusing a fat-primary key so I > didn't have to reallocate one. Thus the entity cache was getting corrupted > because I kept on changing the shared primary key instance. I guess if > you're stupid enough to re-use an instance of a primary key, you deserve to > spend days trying to track down this problem. > > So, if you're going to get rid of the MarshalledObject and all the copying, > why not just get rid of CacheKey all together? > > Bill > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
