precisely the sort of thing we wanna do and likely quite doable by 2.x +1
On Wed, May 30, 2012 at 10:43 PM, Shazron <[email protected]> wrote: > Generally +1 on XHR2, but we're still planning on supporting iOS 4.2 in > Cordova 2.0, so we'll need to shim if not available. > > On Wed, May 30, 2012 at 9:39 PM, Dave Johnson <[email protected]>wrote: > >> Since XHR2 is now available in iOS 5 and Android 3+ >> (http://caniuse.com/#search=xhr) we should probably change all of the >> FileTransfer API to be XHR2 instead of trying to fix the FileTransfer >> API. >> >> Less documentation on our part and standard API ftw. >> >> On Wed, May 30, 2012 at 2:45 PM, Brion Vibber <[email protected]> wrote: >> > On Wed, May 30, 2012 at 1:33 PM, Filip Maj <[email protected]> wrote: >> > >> >> Reference issue: https://issues.apache.org/jira/browse/CB-836 >> >> >> >> I am just fostering discussion here. Maybe a simple `abort` method, a la >> >> XHR [1]? Seems the easiest. >> >> >> >> [1] https://developer.mozilla.org/en/DOM/XMLHttpRequest#abort() >> >> >> > >> > One difficulty is that FileTransfer.upload and FileTransfer.download >> don't >> > appear to return an object which can be used to refer to the ongoing >> > session. >> > >> > If it did, then having an abort method on it would seem perfect! Existing >> > code that didn't understand the object should continue to just work. >> > >> > This would also be a great object on which to addEventListener() for >> > progress events... [2] >> > >> > [2] https://issues.apache.org/jira/browse/CB-622 >> > >> > -- brion vibber (brion @ pobox.com / brion @ wikimedia.org) >>
