Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F2BF6C8AB for ; Tue, 29 Jan 2013 03:07:51 +0000 (UTC) Received: (qmail 21769 invoked by uid 500); 29 Jan 2013 03:07:51 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 21641 invoked by uid 500); 29 Jan 2013 03:07:51 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 21585 invoked by uid 99); 29 Jan 2013 03:07:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jan 2013 03:07:49 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of agrieve@google.com designates 209.85.219.47 as permitted sender) Received: from [209.85.219.47] (HELO mail-oa0-f47.google.com) (209.85.219.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jan 2013 03:07:42 +0000 Received: by mail-oa0-f47.google.com with SMTP id h1so3493403oag.20 for ; Mon, 28 Jan 2013 19:07:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=htdnRaasUehpAbLhezwLAjLhXT2hSRS1GLYi6DaTjWM=; b=fc7cENAykLstSBxJ3X8YBaY2NgRGsP4ePfBJXqElOfs3yZuFRdJR9kPiyJ7/jVntOA xX3Qb+63U/ywkTGh3Y2bASOsebAijdfTPEswSigopnPg78KdGjb1OW44/Lk3Q+1zzast lxaOm9ZnWTWT9Cf1o/FXG67GqW6ut7LJBH91wdvY2L+A3RQ2soe9XbmMaswODcmacDc9 B+C1Oiv/Be0XV3YIUFIA2QC48yemZxVW8JUN1iNAjLS1XOLb9tuz7OTiDvnQwCVS7WMl tS1vmQvbCfrkeWK7MbrZ11RCiN4kBnayEPDWJTm6L9p2cfg8/VPVCTa9+xFAAwUpEnpr QoWg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=htdnRaasUehpAbLhezwLAjLhXT2hSRS1GLYi6DaTjWM=; b=g3Aa0WBS9DO4UqFZ/PEO03gfcE5+cA5igjuu9nC0v4pGSh5MJzAnu6IVUIysxhjexP cA3tpMCASlSlKlFWJPgZEspd0ElNCB5zCqCfBedkvAJOiwYSXoffJdJA5gO1fekIKzDp L7ZufJiTi6GuCFxfT3Td96oj5LNeaAfMbG1CM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :x-gm-message-state; bh=htdnRaasUehpAbLhezwLAjLhXT2hSRS1GLYi6DaTjWM=; b=SWpeEoDQyalYdpl+HvEXijY/JTz7ZHAkG9q8PLqLDeF+BcDO9u52Bzcc7zzOoxWDom PmRNN6sN3kc3WhetdwfxZZh0yeAGpyWTUYilRAsKDurXJ4Rr56OINheVcfHdIYwu8cr7 ThNMvjlhiPFoYTr1WrDbZFC7/WOAsTYQhQasLVsf2kOe98SaJvKJmo0+AuaC1KdRdXaa xUOHLxz46wxDfii08kJiTDjDBi6Ts+FIHLiX6fTfpsOay1mSQxwXNz+IKqdPQPcW0F5q y1R1UXdVujBmmaMNKwguM86Wd9FCJj6C0aZMNwMMq4nwDV+NMd/fcjTQTpfUYp9F7jPq 5wbA== X-Received: by 10.60.24.135 with SMTP id u7mr13119100oef.90.1359428841730; Mon, 28 Jan 2013 19:07:21 -0800 (PST) MIME-Version: 1.0 Sender: agrieve@google.com Received: by 10.182.89.200 with HTTP; Mon, 28 Jan 2013 19:07:01 -0800 (PST) In-Reply-To: References: From: Andrew Grieve Date: Mon, 28 Jan 2013 22:07:01 -0500 X-Google-Sender-Auth: 8tfrPBPdLnNjBU3IN5V1qYvoeZ8 Message-ID: Subject: Re: [Android] xhr2 shim on Android 2.3 - is it worth the effort? I think I need help on this one. To: dev Content-Type: multipart/alternative; boundary=e89a8ff250e63572fa04d464b1dc X-Gm-Message-State: ALoCoQlUETOfzy58WGDu1Vo/SyeX6fbp3SSvXbxGmFPc/kbkov+zXKHmn7pZVdPCWM99Yyf6iHSIS8npzWBW/PjVyLEY7RqAOB6h+9KMwud2na6l+RIWQalioQmiLM7veSDhIuD9Fr5WQc4kUpL4uK+fZIPA44cxDAcJetzKatQdfuyEmTu8i+vRG2vsuksdPj1pzbJkDjoS X-Virus-Checked: Checked by ClamAV on apache.org --e89a8ff250e63572fa04d464b1dc Content-Type: text/plain; charset=ISO-8859-1 Jesse - what's broken about it? On Mon, Jan 28, 2013 at 8:43 PM, Jesse wrote: > Actually the recent checkins break the existing File API that is already > there on Windows 8 and Windows Phone 8. > Both of these platforms already support ArrayBuffers, Blobs, Typed Arrays, > et al ... > > > On Mon, Jan 28, 2013 at 5:09 PM, Andrew Grieve > wrote: > > > The goal of the recent ArrayBuffer work is to allow the browser's native > > ArrayBuffers to be passed through the bridge. It doesn't work on Android > > 2.3, since that version doesn't support ArrayBuffers. > > > > The recent Blob work applied to Cordova's File plugin and made it so that > > it has a slice() method (like the native Blob), and a separate change was > > made so that if you pass a native Blob to FileReader, it will pass > through > > to the native FileReader. > > > > So... Cordova File objects do *not* currently work with xhr2. > > > > I agree that's it's a pretty overwhelming task, and that it's likely not > > worth the effort unless users really start asking for it. > > > > > > > > > > > > On Mon, Jan 28, 2013 at 6:50 PM, Joe Bowser wrote: > > > > > Hey > > > > > > I'm starting to look at adding the xhr2 shim for Android 2.3, and I've > > > come to this conclusion: > > > > > > 1. This looks like a LOT of work and I'm way over my head > > > 2. This depends on a lot of the recent work that was put into Android > > > (ArrayBuffer and Blob) > > > > > > Also, do we know if the new ArrayBuffer and Blob works with Android > > > 4.x xhr2? Doesn't Android 4.x already have an ArrayBuffer and Blob > > > object for it's webview? > > > > > > Anyone want to come in and explain this? This looks pretty > overwhelming. > > > > > > Joe > > > > > > > > > -- > @purplecabbage > risingj.com > --e89a8ff250e63572fa04d464b1dc--