XForms, the xf:header and the HTTP Accept header.

The Mozilla XForms plug-in now, via nightly builds, has support for the
xf:header element and its associated attributes and child elements. With
respect to the HTTP Accept header, the Mozilla implementation appends
the value in the XForm to the request header whilst, for example, the
FormsPlayer implementation overwrites the existing header.

After discussion with Aaron Reed on the dev-tech-xforms mailing list he
suggests that:

> Sounds like you have a usecase for the XForms working group to
consider. 
> Maybe they could put an attribute on the xf:header that says to
replace rather than append.

For my two-penneth worth, after thinking about this for a bit, due to
the nature of an XForms request and the fact that any data bindings will
only be valid for a single representation of the requested resource, the
Accept header should be overridden and therefore only have a single
media type. Multiple media types suggest that the XForm can accept
multiple representations which is of course highly unlike. How you
decide which headers are overridden and which get appended is an
interesting question.

Does anyone on this list have an opinion about this?


Regards

Philip Fennell

http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

Received on Tuesday, 29 July 2008 09:15:32 UTC