cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Unico Hommes" <>
Subject RE: Fooling around with cocoon davmap
Date Mon, 03 Nov 2003 00:57:50 GMT

Sylvain Wallez wrote:
> Unico Hommes wrote:
> >Sylvain Wallez wrote:
> >
> >
> >>Unico Hommes wrote:
> >>
> <snip/>
> >>>I just had a look at the code, seems it was already a FIXME on
> Sylvain's list. Can I go ahead and make this change?
> >>>
> >>>
> >>Uh? Where's that list??
> >>
> >>
> >
> >
> > ln 166/184:
> >// FIXME (SW) : is a flow allowed not to redirect ?
> >
> >;-D
> >
> >
> Uh (again)? I'm wondering if there's not a misunderstanding here: this
> FIXME is about knowing if a flowscript is allowed to terminate without
> stating what page it to be displayed, i.e. check if one of sendPage(),
> sendPageAndWait() or redirectTo() was called.
> Sorry, but I don't see how this relates to HEAD, ETags et al... What
> the change you proposed to do?

We were talking about the fact that it seemed impossible to serve a
request without also sending an entity body along with the response.
(Short of suppressing the output in the serializer which is more of hack
than a solution). I thought it was allowed to call a flow function and
then not send a page. But apparently was wrong. Stefano agreed that it
should be legal to call a flow function that does not redirect to a page
in order to cover the full range HTTP better.

Specifically we were discussing the specification of the OPTIONS method
that prescribes that "the response MUST NOT include entity information
other than what can be considered as communication options" which seems
to exclude sending an entity body from being such a legal response.

I traced the above location as the place the code would need to be
changed in order to achieve this. But I could be wrong.

> BTW, can someone explain me what ETags are about (read that in the
> RFC a long time ago, but did not really understood at that time).

I just looked. It seems entity tags are used as cache validators,
similar to Last-Modified header I guess, i.e. they encode the state of a
resource entity so that clients can optimize network calls by sending
along headers like If-Match, If-None-Match, If-Range, that are then be
checked against the current value of the entity tag on the server. If
they match (or not) the method is executed. At least that's what I got
out of it.

-- Unico

> Sylvain
> --
> Sylvain Wallez                                  Anyware Technologies
> { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
> Orixo, the opensource XML business alliance  -

View raw message