Please excuse my premature send on the preceding email.
>>>>> On Wed, 7 Nov 2012 08:47:37 -0800, Edward Burns <edward.burns_at_oracle.com> said:
>>>>> On Wed, 7 Nov 2012 10:23:00 +0100, Werner Punz <werner.punz_at_gmail.com> said:
WP> To my knowledge the iframe method has the limitations of a normal
WP> form post hence you cannot tamper with the request header, the only
WP> way out of it is not to use iframes but xhr level2 elements for the
WP> multipart upload. But those are only supported in new browsers (aka
WP> even IE9 is not supporting it ie10 does however) and also xhr level2
WP> still is a w3c working draft.
EB> I am takeing XHR level 2 off the table. There is no need to bring
EB> anything about XHR level 2 up again during JSF 2.2.
No sooner had I said this than Manfred on the Mojarra implementation
team requested that I offer the following four options to the EG for
this feature in JSF 2.2.
OPTION_SpecifyNoAjaxFileUpload
Because technically speaking the inline frame method is not really
ajax and never has been, we explicitly declare that using <f:ajax>
with <h:inputFile> is not valid.
OPTION_SpecifyInlineFrame
This is the current plan of record. It requires implementations to
use the inline frame transport to perform file upload if <f:ajax> is
present. We say nothing about XHR but we leave the possibility open
for future revisions.
OPTION_SpecifyXHRLevel2
This was the option suggested by Manfred. We say nothing about the
use of inline frame and, instead, say that jsf.js needs to detect if
XHR Level 2 is available and, if so, we describe how to use it for
file upload.
OPTION_SpecifyInlineFrameOrXHRLevel2
This is the combination of the previous two options.
Personally, I would like to stick with OPTION_SpecifyInlineFrame, but I
wanted to put these other options on the table.
ACTION: Please respond by 12:00 EDT Friday 11 November 2012.
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| homepage: | http://ridingthecrest.com/