Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <4643DB37.8070009@reverycodes.com>
Date: Thu, 10 May 2007 22:55:51 -0400
From: Vadim Gritsenko <vadim@reverycodes.com>
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: More problems with implementing servlet services
References: <4640A55B.8070200@tuffmail.com> <46424753.1020005@nada.kth.se>
In-Reply-To: <46424753.1020005@nada.kth.se>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit

Daniel Fagerstrom wrote:
> Looking at the AbstractProcessingPipeline the getMimeType method of the 
> serializer is called from the setMimeTypeForSerializer method that in 
> turn is called in the beginning of the processXMLPipeline method 
> *before* the generator.generate() method that lead to the actual 
> execution of the serializer. I might be missing something, but AFAICS 
> the call of the setMimeTypeForSerializer method call could be moved to 
> *after* the generator.generate call without changing the result at all.

IIRC, no, this call can't be moved: mime type has to be determined before 
response is generated, because mime type is part of the response header, which 
must be serialized before response data is sent out.

Moving this call means delaying sending response header till complete response 
body is generated and this breaks one of Cocoon's staples -- ability to produce 
response data and send it to the client before complete response is generated.

Vadim