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 bowserj@gmail.com designates
 74.125.82.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CC0F489A.91E6%fil@adobe.com>
References: <4835999501161949975@unknownmsgid>
	<CC0F489A.91E6%fil@adobe.com>
Date: Tue, 26 Jun 2012 11:07:56 -0700
Message-ID: 
 <CAOBL_k6CMHind4u1N1vqyDVrcC6T8Jps4f2xwy29XWUiHWN=MQ@mail.gmail.com>
Subject: Re: XHR2 vs FIleTransfer
From: Joe Bowser <bowserj@gmail.com>
To: callback-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Yes, what about binaries?  I'm wondering how XHR2 handles that, since
it keeps being brought up.

On Tue, Jun 26, 2012 at 11:08 AM, Filip Maj <fil@adobe.com> wrote:
> What about binaries?
>
> On 6/26/12 11:01 AM, "Dan Silivestru" <dan.silivestru@gmail.com> wrote:
>
>>+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. =A0I know that I saw something about Binary Upload,
>>> and I agree that it'd be better to do that. =A0Also, 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
>