Return-Path: Mailing-List: contact turbine-jcs-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list turbine-jcs-user@jakarta.apache.org Received: (qmail 27705 invoked from network); 29 May 2003 12:49:08 -0000 Received: from cs24314-6.austin.rr.com (HELO smtp.drews.tc) (24.243.14.6) by daedalus.apache.org with SMTP; 29 May 2003 12:49:08 -0000 Received: from 192.168.1.120 ([192.168.1.120]) by smtp.drews.tc (JAMES SMTP Server 2.1a1-2002-09-24) with SMTP ID 985 for ; Thu, 29 May 2003 07:47:32 -0500 (CDT) Message-ID: <00b501c325e0$bfa96e80$7801a8c0@fsConnect.org> From: "Heinz Drews" To: "Turbine JCS Users List" References: Subject: To clone or not to clone Date: Thu, 29 May 2003 07:49:30 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hanson, In an earlier message I wrote that I will not answer any more to the other topic. And because the other topic was not correctly describing the matter anyhow I start a new one. > Implementation is easy when it is the right idea. Arriving to the right > idea, however, is hard. And getting the right idea across to others > sometimes is harder. An idea does not get right by simply repeating it. Please just read the chapter 3.1 of the JCache documentation. It clearly says that objects should be shared, one instance per process. And the desired functionality of synchronization cross multiple processes is only achievable if there is only a single instance under the control of the cache manager. It is my opinion that if an object is cloned the implementation is not longer a Cache. And cloning would make the implementation useless for my projects. A second time now this attempt: What has gone wrong in your application that introduced the idea cloning would be the panacea? Best regards, Heinz