Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: Wed, 5 Nov 2003 12:41:53 +0100
Subject: [Vote] empty HTTP responses [was Re: Cannot easily set http status]
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Stefano Mazzocchi <stefano@apache.org>
To: dev@cocoon.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <84F0A43A4248CE45B5C0E20F4C40779C36CC79@naomi.webworks.nl>
Message-Id: <0D3ABD1F-0F85-11D8-A4B9-000393D2CB02@apache.org>


On Wednesday, Nov 5, 2003, at 12:19 Europe/Rome, Unico Hommes wrote:

> setStatus' friends the sendError brothers are also be eligible for FOM
> membership. But this change has a dependency on the discussion about
> bodyless responses since if you'd do a sendError from a flow script and
> then send a page afterwards this would result in errors.

I dislikde "sendError" because, in fact, HTTP does not have the concept 
of errors, but only status codes and empty-payload responses.

In the future, it's entirely possible to have a 309 or equivalent that 
is not an error, but has a empty-payload response. I would dislike to 
call "sendError()" to send something that is not an error, feels hacky.

I think the optimal solution is:

  1) add response.setStatus() in FOM
  2) allow the flowscript to terminate without calling sendPage* [thus 
resulting in an empty payload]

Vote?

--
Stefano.