> idea, however, is hard.  And getting the right idea across to others
> sometimes is harder.

It should be:

getting "what I perceive to be the right idea" across to others is sometimes
harder.


There have been good arguments on both sides for making cloned objects in
the cache, rather than storing object references directly, all made fairly
intellectually, and with a decent amount of forethought.  

There are many intelligent developers with years of Java architecture and
development experience participating in this list and as JCS developers. To
imply your ideas are "right" and theirs are somewhat "wrong" in comparison
is arrogant.  I find the general consensus of many experienced Java
developers in maintaining the current JCS architecture valid evidence that
JCS is a well-thought and well-developed product and doesn't need to be
changed.  Added to, of course (open-source products are never "finished").

There is no right or wrong considering this thread of cloned/serializable
threadsafe objects.  It is a good idea to implement.  It is a bad idea to
change the existing architecture.  There are many good reasons to use either
implementation.

I would suggest in the future, should you want to request a feature or
foster thought for a new architecture, you do so via a cordial proposal.
Your initial email used very strong words similar to JCS "must do this" or
"can't do that", implying the existing JCS implementation was seriously
flawed.  Certain points of the email were arrogant.  Many people work on JCS
for the benefit of others and the satisfaction of knowing they made their
world a little bit better.  Don't attack the work of selfless individuals
because it doesn't meet your needs.  Instead, give back to the project, or
start your own project that meets your needs.  That is the beauty of open
source. 

I apologize if this email comes across in a patronizing or antagonistic
nature, as that is not my intention (e-mail is such a horrible communication
medium for complex discussions).  I, as a complete outsider to JCS (meaning
I haven't coded a single line of it, but use it),  sincerely appreciate your
enthusiasm in bringing forth new ideas that could benefit us all.  Just
please make sure you do it cordially :)

Les

Reply via email to