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 31113 invoked from network); 5 Feb 2003 22:42:28 -0000 Received: from vespa.cmgi.com (206.228.196.11) by daedalus.apache.org with SMTP; 5 Feb 2003 22:42:28 -0000 Received: from EXCHEAST01.enterprise.cmgi.com (excheast01n1.cmgi.com [206.228.196.134]) by vespa.cmgi.com (8.11.6/8.11.6) with ESMTP id h15MgXc22021 for ; Wed, 5 Feb 2003 17:42:33 -0500 (EST) Received: from OWAEAST01.enterprise.cmgi.com ([172.16.1.53]) by EXCHEAST01.enterprise.cmgi.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 5 Feb 2003 17:42:33 -0500 Received: from KBAUM ([206.228.196.210]) by OWAEAST01.enterprise.cmgi.com over TLS secured channel with Microsoft SMTPSVC(5.0.2195.5329); Wed, 5 Feb 2003 17:42:33 -0500 Message-ID: <05b501c2cd67$f57c12f0$5f29f80a@KBAUM> Reply-To: "Karl Baum" From: "Karl Baum" To: Subject: usage Date: Wed, 5 Feb 2003 17:43:00 -0500 Organization: Tallan MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_05AA_01C2CD3E.06FD86A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 05 Feb 2003 22:42:33.0421 (UTC) FILETIME=[DF768FD0:01C2CD67] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------=_NextPart_000_05AA_01C2CD3E.06FD86A0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi I recently discovered JCS and was amazed at all of the features in = the API. I work at a large ecommerce site and was thinking about using = JCS in an upcoming caching project I am leading. I was wondering if = anyone has had any feedback on the stability of the latest release of = JCS or even better some experience using JCS in a production = environment. Any help would be greatly appreciated. =20 Thanks Karl ------=_NextPart_000_05AA_01C2CD3E.06FD86A0--