W3C home > Mailing lists > Public > www-forms@w3.org > April 2006

RE: Addition of submission/@headers

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Tue, 4 Apr 2006 14:30:22 +0100
To: <www-forms@w3.org>
Message-ID: <01d401c657eb$ec654a30$0e01a8c0@Jan>

Allan,

> >       3. All such encodings are concatenated, maintaining document
> >          order.
> 
> I'm not following this. Meaning that all headers will be 
> concatenated, or?

The idea is to copy the terminology used in the part that describes the
serialisation used for 'get'.

So given this:

  <a>
    <b>3</b>
    <c>
      <d>4</d>
    </c>
  </a>

the 'get' serialisation sections uses the term 'encoding' to describe this:

  b=3

Once all such 'encodings' are prepared, they are 'concatenated' with a
separator character between each pair, to produce this:

  b=3&d=4

or this:

  b=3;d=4

(And then of course that's appended to the URL for submission, with a '?' if
needed, but that's not relevant here.)

So my proposal is that for headers the 'encoding' part becomes this:

  b:3

Then as with 'get' all the 'encodings' are 'concatenated', but this time the
separator character between each pair is '\n', which gives us this:

  b:3\nd:4

Which when used in the submission should produce this:

  GET /x ...
  b:3
  d:4
  etc.


> >     If the same element appears Duplicate headers will be created
> 
> "appears more than once, duplicate header" ?

Thanks.

(You can also have duplicate values in 'get', but I thought it worth making
it explicit here because HTTP allows multiple values by simply repeating the
header name with a different value.)

Regards,

Mark


Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
b: http://internet-apps.blogspot.com/
w: http://www.formsPlayer.com/

Download our XForms processor from
http://www.formsPlayer.com/
Received on Tuesday, 4 April 2006 13:31:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:03 GMT