Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 47998 invoked from network); 14 Nov 2003 14:51:28 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 14 Nov 2003 14:51:28 -0000 Received: (qmail 85972 invoked by uid 500); 14 Nov 2003 14:51:20 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 85926 invoked by uid 500); 14 Nov 2003 14:51:20 -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 85912 invoked from network); 14 Nov 2003 14:51:20 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 14 Nov 2003 14:51:20 -0000 Received: (qmail 16987 invoked by uid 50); 14 Nov 2003 14:51:24 -0000 Date: 14 Nov 2003 14:51:24 -0000 Message-ID: <20031114145124.16983.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@cocoon.apache.org Cc: Subject: DO NOT REPLY [Bug 24402] - [PATCH] XML posting from SourceWritingTransformer by using an enhanced HTTPClientSource X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24402 [PATCH] XML posting from SourceWritingTransformer by using an enhanced HTTPClientSource ------- Additional Comments From danielf@nada.kth.se 2003-11-14 14:51 ------- I agree about the source:source-parameter part of your proposal, it seem like a good idea to introduce that for all of the elements: write/insert/delete/post. And also to make it more general so that we have: POST VALUE as you sugested and maybe: VALUE as well for being able to add query parameters to the URI as well. For combining source:post and source:write I am not that certain. The semantics of the source:post is that is first gets the output stream from the modifyable source and writes it XML fragment to it and after that it gets the input stream and add the content of that to the output from the transformer. The source:write just writes to the modifiable source and never asks for its input stream. It is not certain that you want to output the content of e.g. a file that you wrote to. I am not certain that all modifiable sources realy are designed for reading from. So I think it is quite natural to differ between the write and post operation, but maybe we shoud find another name than post as it is coupled to the HTTP-protocol, but I didn't found any better names. Any ideas? WDYT?