Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 77095 invoked by uid 500); 10 Feb 2002 20:33:35 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 77084 invoked from network); 10 Feb 2002 20:33:34 -0000 From: "Mikhail Fedotov" Subject: Re: [RT] Cocoon Symmetry (short :) To: cocoon-dev@xml.apache.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.2 Date: Sun, 10 Feb 2002 23:33:37 +0300 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="KOI8-R" Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi! > Please elaborate more. I don't see what a transformer > isn't able to do in the current implementation. I've been talking that it _can_ do almost the same thing that a symmetric serializer is expected to do, i.e. we can save response to disk, send something somewhere and do virtually anything else in transformer. We don't need specific serializer for that. > But I don't see how this is related to the Subject > "[RT] Cocoon Symmetry". I mean that we [xml/cocoon addicts :)] _already have_ functionality of symmetric serializer via use of transformers, the only deviation is that we still need to wait for some response after request. And this is good since it allows to keep track of request results. That's the point of special symmetric serializer ? Mikhail --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org