Return-Path: Delivered-To: apmail-jakarta-turbine-jcs-user-archive@www.apache.org Received: (qmail 6140 invoked from network); 2 Apr 2004 01:24:29 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Apr 2004 01:24:29 -0000 Received: (qmail 46162 invoked by uid 500); 2 Apr 2004 01:24:12 -0000 Delivered-To: apmail-jakarta-turbine-jcs-user-archive@jakarta.apache.org Received: (qmail 46146 invoked by uid 500); 2 Apr 2004 01:24:12 -0000 Mailing-List: contact turbine-jcs-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Turbine JCS Users List" Reply-To: "Turbine JCS Users List" Delivered-To: mailing list turbine-jcs-user@jakarta.apache.org Received: (qmail 46121 invoked from network); 2 Apr 2004 01:24:11 -0000 Received: from unknown (HELO exchange.ifilm) (63.204.234.22) by daedalus.apache.org with SMTP; 2 Apr 2004 01:24:11 -0000 Received: by exchange.ifilm.com with Internet Mail Service (5.5.2653.19) id ; Thu, 1 Apr 2004 17:23:13 -0800 Message-ID: From: Travis Savo To: 'Turbine JCS Users List' Subject: RE: Finally, JCS updated links. Date: Thu, 1 Apr 2004 17:23:12 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Yes, actually. org.apache.jcs.test.LocalTest was stolen shamelessly from EHCache and adapted for JCS. It's what I used to test the memory and disk caches. The old LocalTest was renamed to CacheTest (I think) as it was woefully inadequate. My goal before the major public release was to write more tests for remote cache. There's also org.apache.jcs.test.CachingWorkerTest, which is a test of a new utility class (org.apache.jcs.CachingWorker) which I use as a bridge and facade for JCS to keep the amount of code to a bare minimum, and ensure maximum efficiency when dealing with operations which will try a cache get first, and result in a cache put if the cache get fails, but may take time between the get and the put (IE Database calls). The CachingWorker wraps the whole 'get, if not there do the work and put' semantics, and ensures that more than one thread doing the same job won't do the work more than once. It's fairly well javadoced, and the unit test asserts all the semantics about it, although they aren't totally obvious from the unit test unless you really take a look at what's going on. Suggestions for how to improve the readability of this test while still asserting all the semantics of it are greatly appreciated. -Travis Savo -----Original Message----- From: Corin Moss [mailto:Corin.Moss@tvnz.co.nz] Sent: Thursday, April 01, 2004 5:08 PM To: Turbine JCS Users List Subject: RE: Finally, JCS updated links. Hi Travis, Thanks for your contribution here - it's greatly appreciated. I'm just trying to "Maven" this code - have you written any test cases for the changes you've made? I'd like to add them to the project definitions if you have - I couldn't see any in the JCS zip :) Thanks, Corin -----Original Message----- From: Travis Savo [mailto:tsavo@IFILM.com] Sent: Friday, 2 April 2004 12:49 p.m. To: 'Turbine JCS Users List' Subject: Finally, JCS updated links. Whereas the demand for my updated code was greater than expected; Whereas I'm getting tired of sending 4 meg worth of attachments to everyone; Whereas some people can't receive 4 meg worth of attachments; Whereas some people probably think this whole thread is a Yet Another April Fools Joke; I've allocated some space on my server and am making the code available for all to download via HTTP. Please don't slashdot this, please don't download it 500 million times, and please don't kill me if at some point in the future (after I get everything's published for real) it goes away. It's not complete by my standards... there's not enough javadoc and documentation for a 1.0 release. But the code itself is being used heavily, WITH 4 remote caches, in a 50 server webfarm, and it's beautiful. Here you go: JCS with no memory leak, no deadlocking disk cache, and a bug free(?) and significantly improved remote cache. http://sindome.org/JCS/JCS.zip Also the link to the EHCache with disk persistence. http://sindome.org/JCS/ehcache-persistent.zip Taking the EHCache persistent disk store and patching it for JCS is left as an exercise to the reader, but as they now share very common code bases (the JCS above uses the original EHCache DiskStore, and the persistent DiskStore is just a mod to that), it should be fairly trivial. Any and all comments are welcome. My goal is to get this stuff remerged into the main JCS codebase, but would love some assistance and feedback before I make it that far. -Travis Savo --------------------------------------------------------------------- To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org ================================================================ CAUTION: This e-mail and any attachment(s) contains information that is intended to be read only by the named recipient(s). It may contain information that is confidential, proprietary or the subject of legal privilege. This information is not to be used by any other person and/or organisation. If you are not the intended recipient, please advise us immediately and delete this e-mail from your system. Do not use any information contained in it. ================================================================ For more information on the Television New Zealand Group, visit us online at http://www.tvnz.co.nz ================================================================ --------------------------------------------------------------------- To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org