Return-Path: X-Original-To: apmail-cocoon-dev-archive@www.apache.org Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1D9D5CEB4 for ; Tue, 29 May 2012 13:11:25 +0000 (UTC) Received: (qmail 62872 invoked by uid 500); 29 May 2012 13:11:24 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 62791 invoked by uid 500); 29 May 2012 13:11:24 -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 List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 62702 invoked by uid 99); 29 May 2012 13:11:24 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 May 2012 13:11:24 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 5154B142837 for ; Tue, 29 May 2012 13:11:24 +0000 (UTC) Date: Tue, 29 May 2012 13:11:24 +0000 (UTC) From: =?utf-8?Q?Francesco_Chicchiricc=C3=B2_=28JIRA=29?= To: dev@cocoon.apache.org Message-ID: <494328350.10872.1338297084336.JavaMail.jiratomcat@issues-vm> In-Reply-To: <2096944724.22521.1330959117500.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Assigned] (COCOON-2320) CachingServletServiceSerializer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COCOON-2320?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiricc=C3=B2 reassigned COCOON-2320: ---------------------------------------------- Assignee: (was: Francesco Chicchiricc=C3=B2) Sorry, I thought issue (and provided patch) were about cocoon-servlet-servi= ce-impl, used by either C2.2 and C3 but only now I see that instead they ar= e related to cocoon-servlet-service-components (C2.2 only). =20 > CachingServletServiceSerializer > ------------------------------- > > Key: COCOON-2320 > URL: https://issues.apache.org/jira/browse/COCOON-2320 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core, - Servlet service framework > Affects Versions: 2.2-dev (Current SVN) > Reporter: Javier Puerto > Priority: Minor > Attachments: CachingServletServiceSerializer.patch > > > Hello Cocoon developers, > We are using Apache Cocoon 2.2 for a project and I've found a bottleneck = in our template system. We use servlet service components to render our pag= es in the same way you can see for Style Block. The current Cocoon Welcome = block is an example. > This way of rendering is very useful but as currently the servlet service= s components doesn't implement CacheableServiceComponent interface, all the= request will be processed completely at the end. > For our usecase, here is an example: > > > > > > The most expensive part is the serialization process because we use i18n,= Link rewriter and some transformations. We can configure everything to be = cacheable but at the end, the serialization process must be performed entir= ely. I've simply extended the current ServletServiceSerializer in CachingSe= rvletServiceSerializer adding the cache key as requested service URL and NO= PValidity as validity object. This approach has a problem, due to the natur= e of the servlet service components we need to move all the dynamically gen= erated content from our GUI block since if we detect that the content hasn'= t changed, the CachingServletServiceSerializer will not perform any process= and will return the cached content. Also, as there's a little hack for ser= ializer output mime type, if you want to use the new component you must set= the serialization content type explicitly. See http://article.gmane.org/gm= ane.text.xml.cocoon.devel/73261 > > > > > > For our usecase seems to fit well and will allow us to enable the powerfu= l cocoon caching system for a lot of pages. IMO, it's a problem when you wa= nt to use the ServletServiceSerializer to have a clean and common output fo= r the template system and you can't use the caching even with static files. > Attached is the patch for cocoon-servlet-service-components block. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp= a For more information on JIRA, see: http://www.atlassian.com/software/jira