Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <46D2A1A7.2050309@apache.org>
Date: Mon, 27 Aug 2007 12:04:23 +0200
From: Grzegorz Kossakowski <gkossakowski@apache.org>
User-Agent: Thunderbird 2.0.0.5 (X11/20070719)
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: http headers
References: <46D20039.10406@tpg.com.au> <46D268C9.4090809@proventis.net>
 <46D27848.4080906@tpg.com.au>
 <1F74BCB22E62024DAF97A048D21822DA38F5E2@UTEX01.be-value.nl>
 <46D2990B.3020301@tpg.com.au> <46D299FF.5090204@apache.org>
 <46D29E9C.4090601@tpg.com.au>
In-Reply-To: <46D29E9C.4090601@tpg.com.au>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

franco pace pisze:
> Hi Grzegorz,
> 
> I have been using cocoon for quite a while developing REST ish web
> services. REST is now gaining
> great momentum. 

Yes, even in Cocoon community, see this[1] e-mail. There has been some work in Cocoon that made 2.2
version much REST-friendly than 2.1.

> REST relies heavily on HTTP protocol and in particular
> in returning specific http status codes
> under certain conditions. For example, say I have a pipeline that
> exposes a db row (or resource):
> 
> <map:match pattern="someentity/*" >
> ...
> 
> Here the * would be an id of some sort.
> 
> so i may wish the GET the entity at url -
> http://myhost/cocoon/someentity/104
> 
> I would like for example, to set the http status code to 403 if the
> client does not
> have authority to view the data, and to say 404 if the entity does not
> exist (not found).

Why not to use flowscript for this?

[1] http://article.gmane.org/gmane.text.xml.cocoon.devel/74571

-- 
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org