[
https://issues.jboss.org/browse/RF-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12961581#comment-12961581
]
Michal Petrov commented on RF-13514:
------------------------------------
[~jhuska], after my commits, are there any remaining issues on WildFly 8 Final?
As far as AS 7.1.1 is concerned it seems there are issues with more components
than just fileUpload.
> Support file upload progress tracking in Servlets >= 3.0 environment
> --------------------------------------------------------------------
>
> Key: RF-13514
> URL: https://issues.jboss.org/browse/RF-13514
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-input, core
> Affects Versions: 5.0.0.Alpha3
> Reporter: Lukáš Fryč
> Assignee: Michal Petrov
> Fix For: 4.5.0.Alpha3
>
>
> We currently support two approaches for file upload:
> * Servlets 2.5: own request form data parser
> [{{MultipartRequestParser}}|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/request/MultipartRequestParser.java]
> * Servlets 3.0: leveraging {{HttpServletRequest#getParts()}}
> However as we have discussed RF-13444, we had to finally do a trade-off of
> limiting support of file progress tracking. I.e. in Servlets 3.0 we have no
> simple way how to track file upload progress since getParts() returns data
> for completed request.
> There are several possible outcomes:
> 1) drop server-side file upload progress tracking and leverage XHR2/HTML5
> that has built-in ability to track progress
> * imho we are already prepared to switch to XHR2 and client-side progress
> (possibly leveraging some third-party widget) since [all major browsers
> support it at least one version back|http://caniuse.com/#feat=xhr2]
> * existing implementation:
> http://www.script-tutorials.com/pure-html5-file-upload/
> 2) use a {{ServletFilter}} to wrap a request as our
> {{FileUploadFacesContextFactory}} currently do and so have an earlier access
> to the request object
> * this principle has a drawback - we have to ensure our filter has
> high-enough priority so the servlet container won't touch the request body yet
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
