Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 35074 invoked from network); 10 Mar 2004 04:03:02 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 10 Mar 2004 04:03:02 -0000 Received: (qmail 63375 invoked by uid 500); 10 Mar 2004 04:02:39 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 63322 invoked by uid 500); 10 Mar 2004 04:02:39 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 63307 invoked from network); 10 Mar 2004 04:02:39 -0000 Received: from unknown (HELO warden.diginsite.com) (208.29.163.248) by daedalus.apache.org with SMTP; 10 Mar 2004 04:02:39 -0000 Received: from wlvims01.diginsite.com by warden.diginsite.com via smtpd (for daedalus.apache.org [208.185.179.12]) with SMTP; Tue, 9 Mar 2004 20:02:49 -0800 Received: from WLVIMS01 ([127.0.0.1]) by WLVIMS01.digitalinsight.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with SMTP id com for ; Tue, 9 Mar 2004 20:02:48 -0800 Received: by calexc01.diginsite.com with Internet Mail Service (5.5.2657.72) id ; Tue, 9 Mar 2004 20:01:50 -0800 Message-ID: <31DF72A980E5D511B48C000102BD8685061DB284@calexc01.diginsite.com> From: Ralph Goers To: "'dev@cocoon.apache.org'" Subject: RE: Store options Date: Tue, 9 Mar 2004 20:01:42 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/mixed; boundary="----=_NextPartTM-000-82e9006d-1c94-4c06-ba7f-50922fc34cad" 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 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------=_NextPartTM-000-82e9006d-1c94-4c06-ba7f-50922fc34cad Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C40654.656D2DD0" ------_=_NextPart_001_01C40654.656D2DD0 Content-Type: text/plain Would it be possible to implement this as a plugin in Cocoon? This could be done by requiring adherence to the current JSR 107 spec (assuming you can find it). While the default could be JCS, other alternatives are jcache.sourceforge.net, Tangosol Coherence, Spiritsoft and who knows what else. This would also make it easier to swap to another caching implementation should JCS turn out to have significant problems. Since we are already using Tangosol in our EJB container it would be nice to be able to leverage it in Cocoon as well. I'm assuming, of course, that JCS isn't providing stuff beyond JSR 107 that you absolutely need. Ralph -----Original Message----- From: Corin Moss [mailto:Corin.Moss@tvnz.co.nz] Sent: Tuesday, March 09, 2004 6:42 PM To: dev@cocoon.apache.org Subject: Store options Hi Guys, Sorry to bring this one up again, has anyone given any more thought to options for a cache / store implementation? My feeling at the moment is that JCS is the best of an imperfect bunch. There are definitely some problems in its implementation of JSR-107, but I really like the functionality it does have. From what I can tell, JCS has not been very well cared for over the last year or so. The core developers don't have a lot of time to work on it. Is there any way we can get the ASF to (perhaps) take JCS out of Turbine and put it into an incubator of its own, or promote JCS as a project as part of Cocoon or Avalon? I really think that there is some great work done there, in danger of getting lost. It is certainly a better approach (IMHO) than starting off developing another caching / store system. WDYT? Corin Corin Moss Lead Developer TVNZ Interactive +64 9 916 7367 +64 21 403 054 corin.moss@tvnz.co.nz ================================================================ 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 ================================================================ ------_=_NextPart_001_01C40654.656D2DD0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable Store options

W= ould it be possible to implement this as a plugin in Cocoon?  This could be done by requiring adherence to the = current JSR 107 spec (assuming you can find = it).

<= ![if = !supportEmptyParas]> 

=

W= hile the default could be JCS, other alternatives are jcache.sourceforge.net, = Tangosol Coherence, Spiritsoft and who knows what else.  This would also make it easier to swap to another = caching implementation should JCS turn out to have significant = problems.

<= ![if = !supportEmptyParas]> 

=

S= ince we are already using Tangosol in our EJB container it would be nice to be = able to leverage it in Cocoon as well.

<= ![if = !supportEmptyParas]> 

=

I= ’m assuming, of course, that JCS isn’t providing stuff beyond JSR = 107 that you absolutely need.

<= ![if = !supportEmptyParas]> 

=

R= alph

<= ![if = !supportEmptyParas]> 

=

-----Original Message-----
From: Corin Moss [mailto:Corin.Moss@tvnz.co.nz]
Sent: Tuesday, March 09, = 2004 6:42 PM
To: = dev@cocoon.apache.org
Subject: Store = options

 

Hi Guys,

Sorry to bring this one up again, has = anyone given any more thought to options for a cache / store = implementation?  My feeling at the moment is that JCS is the best of an imperfect bunch.   There are definitely some problems in its = implementation of JSR-107, but I really like the functionality it does have.  From = what I can tell, JCS has not been very well cared for over the last year or = so.  The core developers don't have a lot of time to work on it.  Is = there any way we can get the ASF to (perhaps) take JCS out of Turbine and put it = into an incubator of its own, or promote JCS as a project as part of Cocoon or = Avalon?=

I really think that there is some great = work done there, in danger of getting lost.  It is certainly a better = approach (IMHO) than starting off developing another caching / store = system.=

WDYT?

Corin

Corin Moss
Lead Developer
TVNZ Interactive

+64 9 916 7367
+64 21 403 054
corin.moss@tvnz.co.nz =

 =

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
For more information on the Television New Zealand Group, visit
us online at http://www.tvnz.co.nz
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
------_=_NextPart_001_01C40654.656D2DD0-- ------=_NextPartTM-000-82e9006d-1c94-4c06-ba7f-50922fc34cad--