Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of dan.silivestru@gmail.com
 designates 209.85.212.177 as permitted sender)
References: 
 <397462593-1340733493-cardhu_decombobulator_blackberry.rim.net-849407335-@b13.c19.bise6.blackberry>
From: Dan Silivestru <dan.silivestru@gmail.com>
In-Reply-To: 
 <397462593-1340733493-cardhu_decombobulator_blackberry.rim.net-849407335-@b13.c19.bise6.blackberry>
Mime-Version: 1.0 (1.0)
Date: Tue, 26 Jun 2012 14:01:25 -0400
Message-ID: <4835999501161949975@unknownmsgid>
Subject: Re: XHR2 vs FIleTransfer
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

+1

Dan Silivestru
+1 (519)-589-3624

On 2012-06-26, at 13:58, "gtanner@gmail.com" <gtanner@gmail.com> wrote:

> I would vote we should go with XHR2 and polyfill it into the platforms it isn't supported.
> ------Original Message------
> From: Joe Bowser
> To: callback-dev@incubator.apache.org
> ReplyTo: callback-dev@incubator.apache.org
> Subject: XHR2 vs FIleTransfer
> Sent: Jun 26, 2012 1:39 PM
>
> Hey
>
> I know that we've been debating this, but I'm wondering if we're
> abandoning/deprecating FileTransfer in favor for XHR2 and what the
> pros and cons are.  I know that I saw something about Binary Upload,
> and I agree that it'd be better to do that.  Also, there are numerous
> tickets regarding FileTransfer that people want looked at, and I'm
> wondering if I should prioritize them for 2.0 or if I should close
> them and say that XHR2 is the way of the future and that they're
> welcome to fork this off as a plugin.
>
> In short, what are we doing with this?
>
> Joe
>
> Sent on the TELUS Mobility network with BlackBerry