Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 54567 invoked from network); 25 Jan 2006 14:45:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Jan 2006 14:45:55 -0000 Received: (qmail 88383 invoked by uid 500); 25 Jan 2006 14:45:53 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 88183 invoked by uid 500); 25 Jan 2006 14:45:52 -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 88172 invoked by uid 99); 25 Jan 2006 14:45:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jan 2006 06:45:52 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [84.96.21.10] (HELO mail.anyware-tech.com) (84.96.21.10) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jan 2006 06:45:49 -0800 Received: from localhost (localhost [127.0.0.1]) by mail.anyware-tech.com (Postfix) with ESMTP id 9C19F33BF1 for ; Wed, 25 Jan 2006 15:45:28 +0100 (CET) Received: from mail.anyware-tech.com ([127.0.0.1]) by localhost (trinity [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31292-03 for ; Wed, 25 Jan 2006 15:45:25 +0100 (CET) Received: from [10.0.0.27] (poukram.anyware [10.0.0.27]) by mail.anyware-tech.com (Postfix) with ESMTP id 4FC6333BF5 for ; Wed, 25 Jan 2006 15:45:23 +0100 (CET) Message-ID: <43D78F04.9000505@apache.org> Date: Wed, 25 Jan 2006 15:45:24 +0100 From: Sylvain Wallez User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [blocks] Changing component strategy References: <43D68185.1070907@nada.kth.se> <43D6881B.8020503@apache.org> In-Reply-To: <43D6881B.8020503@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at anyware-tech.com X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Carsten Ziegeler wrote: > Daniel Fagerstrom wrote > >> WDYT? >> >> > I'm not sure if a global registry really works. What happens if I want > to use a block twice but with different configurations? Can this be handled? > Yep. How do we (can we) implement the classical scenario that's been considered for blocks, i.e. the skinning with a "multi-skin" that delegates to other skin blocks. In that scenario, application blocks depend on a block implementing the "skin" contract, and the implementation chooses the actual skin block to be used depending on some condition (user, time, host, whatever). That means we'll have 3 implementations of the "skin" block interface in the system, and possibly have several different instances of the e.g. "myCorporateSkin" block with different configurations (color, stylesheets, etc). Sylvain -- Sylvain Wallez Anyware Technologies http://bluxte.net http://www.anyware-tech.com Apache Software Foundation Member Research & Technology Director