>> (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: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
