[
Lists Home |
Date Index |
Thread Index
]
Hi Bjoern,
Bjoern said:
> >From a performance point of view, this does not make sense. Generate
> your static documents once, not millions of times. Generate them on
> your own, don't let millions of clients do it for you again and again.
Didier replies:
So your point is that tools like cocoon are useless. There is also the
possibility to cache the transformed document so that it is available in its
transformed format for the next time. However, if the transformation is
performed using parameters given by the user agent[1]1 then, you have no
choices than to dynamically create it each time. For instance, a URL may
contain a parameter specifying that the user wants some information units
but not other ones. The stylesheet associated to the document may act - in
this case - as a filter selecting fragments from the original XML document
and including them in the destination document, possibly transforming the
destination document for rendition on the user agent.
Didier said:
> >expected to find that in cocoon but couldn't find that feature in this
> >server extension. It seems that cocoon handles only the "user-agent"
pattern
> >match but not the "accept" request. Maybe I am wrong and didn't checked
at
> >the right place and I'll do a second reading but up to now, no, cocoon
seems
> >to not be totally compliant with the HTTP 1.1 specs, at least when it is
a
> >question of dynamic transformations based on the user agent format
> >requirements.
Bjoern replied:
> This does not relate to HTTP user agent compliance.
Didier replies:
I am sorry Bjoern but it is. Just read the following document[2] and more
particularly the section 14. If we follow the specs, the server receiving an
accept header specifying that the only accepted format is "text/svg"
*should* provide this format to the user agent if the server can do that
(off course won't if it can't). By "can do that" I mean there exist either a
static SVG version of the document or that the server can dynamically create
one. The server *should* *as much as possible* provide a format the user
agent "accept" for rendition.
cheers
Didier PH Martin
[1] I mean here the URL parameters not the HTTP headers.
[2] http://www.w3.org/Protocols/HTTP/1.1/rfc2616.pdf.
>
|
