[ 
https://issues.apache.org/jira/browse/CB-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448922#comment-13448922
 ] 

Andrew Grieve commented on CB-622:
----------------------------------

I did some more investigation into the state of gzip.

The case right now on Android is that gzip does not happen on older version 
(pre-froyo I think). And on newer version it happens transparently. If we set 
the accept-encoding:gzip header ourselves on the connection, then it will not 
do the transparent handling of gzip, and we need to deflate it ourselves. This 
is good news because it means we can do as the stackoverflow article suggests 
in order to track get progress of the download.

The case for iOS though, is that there is no way to track the actual bytes 
downloaded except for moving network stacks to something like ASI's. I'm 
wondering if in this case a decent option is to re-gzip the response locally to 
approximate. :P seems lame though, and I think we'd want to wait for users to 
ask for this first.
                
> FileTransfer interface should provide progress monitoring
> ---------------------------------------------------------
>
>                 Key: CB-622
>                 URL: https://issues.apache.org/jira/browse/CB-622
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Android, BlackBerry, iOS, WP7
>    Affects Versions: 1.7.0
>         Environment: Checked docs for iOS and Android, and in general.
>            Reporter: Brion Vibber
>            Assignee: Andrew Grieve
>            Priority: Minor
>              Labels: FileTransfer, file
>
> The FileTransfer upload and download interface seems to provide no way to 
> monitor progress of the upload/download, other than waiting for the entire 
> transfer to complete or fail.
> Being able to pass another callback for progress monitoring could be a useful 
> interface, this might get called with a byte count or something.

--
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

Reply via email to