Return-Path: 
 <cocoon-dev-return-29042-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 54826 invoked by uid 500); 3 Jul 2002 11:49:07 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 54815 invoked from network); 3 Jul 2002 11:49:06 -0000
Date: Wed, 3 Jul 2002 07:48:20 -0400
Subject: Re: [RT] reconsidering pipeline semantics
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
From: Jason Foster <jafoster@uwaterloo.ca>
To: cocoon-dev@xml.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <88ABF0CB-8E65-11D6-9C21-0003935AD2EE@mac.com>
Message-Id: <C5BA292E-8E7A-11D6-894E-000A27E14D02@uwaterloo.ca>
X-Mailer: Apple Mail (2.482)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

>> (3) using a pipeline as a serializer

Wouldn't this be useful for having authenticated and non-authenticated 
versions of resources?  Something like...

<pipeline name="sign">
     <transform ../> <!-- add in security info via xml-sig -->
     <serialize ../> <!-- generate output and save signature somewhere -->
</pipeline>

<pipeline>
     <match pattern="*">
      <generate ../>
      <tranform ../>
      <call pipeline="sign"/>
     </match>
</pipeline>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org