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.39 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Date: Mon, 27 Feb 2012 11:39:02 -0800
Subject: Re: Changes to requesting a PERSISTENT file system in
 Cordova-Android
Thread-Topic: Changes to requesting a PERSISTENT file system in
 Cordova-Android
Thread-Index: Acz1h3aYhp4hWH7zQ6+UTy2Fhbmwtw==
Message-ID: <CB711AB8.5A52%fil@adobe.com>
In-Reply-To: 
 <CAM1AYQDYTHG5=i7EHGyhmjs-W4diDTn9OCmVdZ3r9Et+9_rWZw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I'm not sure if it needs to go to vote... Maybe if there is enough
contention on the topic?

How about let's revert the temp/persistent resolution on android to what
it was before (if it hasn't already been done) so we don't freak users
out. Then let's use this thread to figure out the details of how it
*should* be done on Android. Once we have it figured out, document on wiki
and put it in the roadmap (is that the place to document these sorts of
api changes?)

On 12-02-27 6:06 AM, "Simon MacDonald" <simon.macdonald@gmail.com> wrote:

>But I guess the immediate question is do we want to make this change for
>1.5 or publicize we are making the change for a future release? Does this
>need to go with a vote?
>
>Simon Mac Donald
>http://hi.im/simonmacdonald
>
>
>On Wed, Feb 22, 2012 at 5:27 PM, Filip Maj <fil@adobe.com> wrote:
>
>> This is a good discussion to have. Blindly following a spec never gets
>>you
>> 100% where you want to go.
>>
>> Instead: what are reasonable storage options that as a developer using
>> cordova you would like to see? Once that is decided on, define a simple
>> spec for each of the options.
>>
>> So for the first question, in my mind having an idea of a "temporary"
>> storage space - like Joe said, volatile memory - and "persistent" seem
>> like two good options.
>>
>> Then, for simple constraints around the two options:
>>
>> To me, persistent is: data that I write to a persistent location is
>> available across device restarts and will not be removed unless my
>> application explicitly removes it (barring exceptional circumstances
>>such
>> as a device factory reset). The Android "Jail" is, for me, a good
>> candidate to be considered the persistent storage location. A removable
>> storage type such as an SD or media card is, in my mind, not a candidate
>> to "persistent" storage.
>>
>> For temporary storage, the restrictions are much less. Figuring out any
>> minimum time frames for how long a temporary storage location exists
>>seems
>> important. Should temporary storage be guaranteed across device
>>restarts?
>> Probably not. What about across application restarts? I'm not sure - I
>> would say no, not guaranteed. Within an application session? I think so.
>>
>> Etc. etc. :)
>>
>>