Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Date: Wed, 24 Oct 2012 18:24:12 +0000 (UTC)
From: "Andrew Grieve (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: <2049253474.23068.1351103052094.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <1829511484.15023.1335909049798.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CB-622) FileTransfer interface should provide
 progress monitoring
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Hey Greg, thanks for asking! I looks like updating the docs was overlooked. I've created a new bug to do so: https://issues.apache.org/jira/browse/CB-1704
                
> 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
>             Fix For: 2.2.0
>
>
> 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