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 fil@adobe.com designates
 64.18.1.31 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Date: Tue, 12 Jun 2012 15:48:25 -0700
Subject: Re: FileTransfer header support and options
Thread-Topic: FileTransfer header support and options
Thread-Index: Ac1I7WCrS5Xl4/ezRCOgKdN5jWrS0A==
Message-ID: <CBFD14EC.8057%fil@adobe.com>
In-Reply-To: 
 <CADVgkyODOg4dudc9ELxVk0CL+han2B=m5=F9i__m28i49ftZ9w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.2.120421
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Media needs a revision (can we drop and adopt a friendlier spec?).
Compass' spec has changed. I think the network status one has as well. I
have no idea about File but, probably. Devicemotion/orientation vs
accelerometer.. Contacts have been updated too. XHR2 vs our own
FileTransfer. Pretty much all of them haha.

On 6/12/12 3:44 PM, "Brian LeRoux" <b@brian.io> wrote:

>> Once we ship 2.0 we need a revision of _all_ APIs pretty badly. Lots of
>> specs have been updated/revised. Review the mobile landscape. See what
>> direction/specs the functionalities we aim to provide with cordova are
>> going and polyfill those for our users.
>
>This is true. The sys-apps group in particular is going to have stuff
>for us to impl. Think the DAP APIs are going to fade.