Return-Path: Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 3324 invoked by uid 500); 6 Jul 2003 20:38:03 -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 3310 invoked from network); 6 Jul 2003 20:38:03 -0000 Received: from smtp8.wanadoo.fr (HELO mwinf0102.wanadoo.fr) (193.252.22.30) by daedalus.apache.org with SMTP; 6 Jul 2003 20:38:03 -0000 Received: from anyware-tech.com (AToulouse-206-1-7-141.w81-50.abo.wanadoo.fr [81.50.197.141]) by mwinf0102.wanadoo.fr (SMTP Server) with ESMTP id DC9951BFD3E8 for ; Sun, 6 Jul 2003 22:38:07 +0200 (CEST) Message-ID: <3F0888B1.2000103@anyware-tech.com> Date: Sun, 06 Jul 2003 22:38:09 +0200 From: Sylvain Wallez Organization: Anyware Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: fr, en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [Flow] Calling internal-only pipelines References: <000a01c33c6f$e691b110$1e01a8c0@WRPO> <4708D5A4-A881-11D7-AFAD-0003935AD2EE@media.demon.co.uk> <3F02E58A.6050905@anyware-tech.com> <3F034763.5080405@anyware-tech.com> <3F080D5C.3040809@anyware-tech.com> <3F08824E.1000800@cbim.it> In-Reply-To: <3F08824E.1000800@cbim.it> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Ugo Cei wrote: > Sylvain Wallez wrote: > >> Done. You can now have flow views in internal-only pipelines ! > > > Excellent! Thanks ! After more thinking about this new Request.isInternal(), I found that this notion of "internal request" isn't precise enough to be of real use, and worse, may lead to dangerous confusion if used to filter headers as I suggested earlier. Here are some examples of statements that produce internal requests : 1 - 2 - cocoon.sendPageAnddWait("blah"); 3 - 4 - (in a ) 5 - What we see here is that : - 1, 2 are "internal", but actually provide the content returned to the browser. - 3 and 4 can be discussed : is it a chained pipeline (meaning we could accept headers from "blah"), or just a dynamic resource ? - 5 is clearly not targeted to the browser. So, to avoid this confusion, I removed the newly added Request.isInternal() and added Environment.isExternal(). An external environment is the one whose creation is triggered by the external request (http, commandline, etc). Putting this method on Environment hides it from "regular" components and as such avoids the possible confusion mentioned above. But the result is still that flow views can be internal-only pipelines ;-) Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com