Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of fil@adobe.com designates
 64.18.1.191 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Date: Fri, 29 Jun 2012 11:30:54 -0700
Subject: Re: [Android] Do we need to manage our own history?
Thread-Topic: [Android] Do we need to manage our own history?
Thread-Index: Ac1WJRemjQ6Z5SbgRoqhev9zUZMweg==
Message-ID: <CC13425D.96BF%fil@adobe.com>
In-Reply-To: 
 <CAOBL_k51OW7V+ogWZnSeUP55ZCPtnDhJKE0MfCUef-WqsF+0gg@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

If built-in history cuts it then yeah, I'm all for deprecating/removing.

On 6/29/12 11:26 AM, "Joe Bowser" <bowserj@gmail.com> wrote:

>Now that I merged in the fix for params on Android 4.0.x (need to test
>if this bug is fixed in 4.1), I want to see if we can remove our
>Android history and the handling, since this is a lot of fragile code
>that I would prefer to have deprecated.  It'd be nice to do this in
>2.0
>
>Any thoughts on this?
>
>Joe