W3C home > Mailing lists > Public > xproc-dev@w3.org > April 2010

Re: Influencing namespace declaration in HTTP PUT

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 16 Apr 2010 16:45:54 -0400
To: XProc Dev <xproc-dev@w3.org>
Message-ID: <m2iq7runwd.fsf@nwalsh.com>
Florent Georges <fgeorges@fgeorges.org> writes:
> On 15 April 2010 12:18, Norman Walsh wrote:
>
>> The p:http-request step has all the serialization options. Did
>> we miss something?
>
>   Quite embarrassing: *I* missed the fact you followed the same
> path actually.  But in XProc, the serialization parameters are at
> the level of the HTTP request itself, instead of the level of the
> body content.  That means it is not suitable for multipart.
> E.g. the typical case where you want a multipart/alternative
> where one part is text/html and the other text/plain (so @method
> must be once "html" and the other one "text").

Ah, right. I think we may have decided that that was a bridge too far
for V1.0. The only serious multipart POST pipeline that I've written
was a mixture of text/plain and image/jpg, so I didn't notice.

I suppose you could get differently serialized parts by careful use of
p:unescape-markup steps. Maybe.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | 'I have done that,' says my memory. 'I
http://nwalsh.com/            | cannot have done that'--says my pride,
                              | and remains adamant. At last--memory
                              | yields.-- Nietzsche

Received on Friday, 16 April 2010 20:46:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 16 April 2010 20:46:27 GMT