Make status code attribute of seriailzers expandable

[Ard Schrijvers <a....@hippo.nl>]

I missed the discussion before the vote, but have one more question:

Is it also possible to add extra optional http headers in the serializer, like:

<map:serialize type="xhtml" pragma="{cache}" cache-control="{cache}">

I would like to store in a variable wether I am dealing with something that is not allowed to be cached by mod_cache, like a cforms with continuation. We had a discussion before on this list, but cannot find the thread ATM

I do not know about the serializers, but is this possible and/or desirable? 

Ard


> 
> Reinhard Poetz wrote:
>  > Vadim Gritsenko wrote:
>  >> Reinhard Poetz wrote:
>  >>>
>  >>> Is there a specific reason why this patch 
> (http://issues.apache.org/jira/browse/COCOON-1354) has never 
> been applied?
>  >>
>  >> Technically, other than rewriting the last chunk of the 
> patch, it looks Ok. 
>  From procedure POV, I don't recall a VOTE on that. Previous 
> decision on what 
> can be expandable in the sitemap was VOTEd upon.
>  >
>  > I will start a vote on this then. Any opinions in the meantime?
> 
> I don't see reason why not, even if not needed often.
> 
> Vadim
> 
>  > My usecase is that I want to provide REST-style 
> webservices with Cocoon and 
> knowing which status code to set is part of the business logic.
> 
> 
>                                    - o -
> 
> 
> I propose making the status code attribute of serializers 
> expandable. This makes 
> it easier to provide REST style services with Cocoon that 
> make use of the 
> different meanings of status codes.
> 
> -- 
> Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 
> 
> {Software Engineering, Open Source, Web Applications, Apache Cocoon}
> 
>                                         web(log): http://www.poetz.cc
> --------------------------------------------------------------------
> 

Re: Make status code attribute of seriailzers expandable

[Grzegorz Kossakowski <gk...@apache.org>]

Ard Schrijvers napisał(a):
> I missed the discussion before the vote, but have one more question:
>
> Is it also possible to add extra optional http headers in the serializer, like:
>
> <map:serialize type="xhtml" pragma="{cache}" cache-control="{cache}">
>
> I would like to store in a variable wether I am dealing with something that is not allowed to be cached by mod_cache, like a cforms with continuation. We had a discussion before on this list, but cannot find the thread ATM
>   
I'm -1 for setting this in a serializer.
> I do not know about the serializers, but is this possible and/or desirable? 
>   

I was going to propose the same but set on pipeline level. Then one
would group pipelines sharing the same caching characteristics. We have
already "expires" parameter for pipelines so I think it fits into
current design.
As servlet sevice stuff demands high conformity with HTTP specification
I'm all +1 on such addition.

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

Re: Make status code attribute of seriailzers expandable

[Vadim Gritsenko <va...@reverycodes.com>]

Ard Schrijvers wrote:
> I missed the discussion before the vote, but have one more question:
> 
> Is it also possible to add extra optional http headers in the serializer, like:
> 
> <map:serialize type="xhtml" pragma="{cache}" cache-control="{cache}">
> 
> I would like to store in a variable wether I am dealing with something that is not allowed to be cached by mod_cache, like a cforms with continuation. We had a discussion before on this list, but cannot find the thread ATM
> 
> I do not know about the serializers, but is this possible and/or desirable? 

Please see HttpHeaderAction, can set any response header you want

Vadim