Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 2747 invoked by uid 500); 18 Jun 2003 07:11:07 -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 2721 invoked from network); 18 Jun 2003 07:11:06 -0000 Received: from unknown (HELO mail.cbim.it) (212.131.130.82) by daedalus.apache.org with SMTP; 18 Jun 2003 07:11:06 -0000 Received: from cuprouter.cbim.it (cuprouter.cbim.it [192.168.4.10]) by mail.cbim.it (8.11.6/8.11.0) with ESMTP id h5I7Yh627475 for ; Wed, 18 Jun 2003 09:34:44 +0200 Received: from cbim.it (caterina.cbim.it [192.168.4.42]) by cuprouter.cbim.it (8.9.3/8.9.3) with ESMTP id JAA22160 for ; Wed, 18 Jun 2003 09:12:27 +0200 Message-ID: <3EF010C7.1070304@cbim.it> Date: Wed, 18 Jun 2003 09:12:07 +0200 From: Ugo Cei Organization: C.B.I.M. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: Linotype editing: browser requirements? References: <4772090E-A089-11D7-A52A-000393CFE402@codeconsult.ch> <3EEEC77C.1050205@outerthought.org> <3EEF16AE.7080106@outerthought.org> <3EEF7FFC.4000605@outerthought.org> <3EEF9410.9060102@apache.org> In-Reply-To: <3EEF9410.9060102@apache.org> 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 Stefano Mazzocchi wrote: > No, no need for that. It took me half an hour to figure that problem out > myself and it's an indication of how generally badly designed is > cocoon's handling of multipart-encoded POST requests. Could it be useful to document this "feature" along with the usage instructions? Anyway, I'm wondering why the multipart request. Is it because of images? If it weren't for images, wouldn't it be better to POST a text/xml body with all the necessary information, putting the "verb" (save, delete, etc.) in the URI, in the style of REST? Ugo -- Ugo Cei - http://www.beblogging.com/blog/