Re: Changes to requesting a PERSISTENT file system in Cordova-Android

[Brian LeRoux <b...@brian.io>]

bump. my $0.02. we have two choices: relative or protocol handler.

rel means devs have to construct paths from (brittle) strings and
concatenating ... using app ids, etc. less extensible.

i'd like to push we gun for protocol handlers for app level and root to start:

app://
root://

in the future we could add discovery for things like:

sdcard://



On Mon, Feb 27, 2012 at 11:39 AM, Filip Maj <fi...@adobe.com> wrote:
> 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" <si...@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 <fi...@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. :)
>>>
>>>
>

Re: Changes to requesting a PERSISTENT file system in Cordova-Android

[Filip Maj <fi...@adobe.com>]

>Remember that. Maybe we throw this to a vote?

+1 

>
>On Tue, Mar 6, 2012 at 9:19 PM, Bryce Curtis <cu...@gmail.com>
>wrote:
>> We can discuss how these protocols translate to various platforms, but I
>> think it makes sense.  We had a discussion similar to this back when we
>> were looking at the File APIs.  See the wiki for some of what we
>> discussed...
>> http://wiki.phonegap.com/w/page/35605874/Planning%3A%20File%20API
>>
>>
>> On Tue, Mar 6, 2012 at 6:54 PM, Brian LeRoux <b...@brian.io> wrote:
>>
>>> bump. my $0.02. we have two choices: relative or protocol handler.
>>>
>>> rel means devs have to construct paths from (brittle) strings and
>>> concatenating ... using app ids, etc. less extensible.
>>>
>>> i'd like to push we gun for protocol handlers for app level and root to
>>> start:
>>>
>>> app://
>>> root://
>>>
>>> in the future we could add discovery for things like:
>>>
>>> sdcard://
>>>
>>>
>>>
>>> On Mon, Feb 27, 2012 at 11:39 AM, Filip Maj <fi...@adobe.com> wrote:
>>> > 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" <si...@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 <fi...@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. :)
>>> >>>
>>> >>>
>>> >
>>>

Re: Changes to requesting a PERSISTENT file system in Cordova-Android

[Brian LeRoux <b...@brian.io>]

Remember that. Maybe we throw this to a vote?


On Tue, Mar 6, 2012 at 9:19 PM, Bryce Curtis <cu...@gmail.com> wrote:
> We can discuss how these protocols translate to various platforms, but I
> think it makes sense.  We had a discussion similar to this back when we
> were looking at the File APIs.  See the wiki for some of what we
> discussed...
> http://wiki.phonegap.com/w/page/35605874/Planning%3A%20File%20API
>
>
> On Tue, Mar 6, 2012 at 6:54 PM, Brian LeRoux <b...@brian.io> wrote:
>
>> bump. my $0.02. we have two choices: relative or protocol handler.
>>
>> rel means devs have to construct paths from (brittle) strings and
>> concatenating ... using app ids, etc. less extensible.
>>
>> i'd like to push we gun for protocol handlers for app level and root to
>> start:
>>
>> app://
>> root://
>>
>> in the future we could add discovery for things like:
>>
>> sdcard://
>>
>>
>>
>> On Mon, Feb 27, 2012 at 11:39 AM, Filip Maj <fi...@adobe.com> wrote:
>> > 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" <si...@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 <fi...@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. :)
>> >>>
>> >>>
>> >
>>

Re: Changes to requesting a PERSISTENT file system in Cordova-Android

[Bryce Curtis <cu...@gmail.com>]

We can discuss how these protocols translate to various platforms, but I
think it makes sense.  We had a discussion similar to this back when we
were looking at the File APIs.  See the wiki for some of what we
discussed...
http://wiki.phonegap.com/w/page/35605874/Planning%3A%20File%20API


On Tue, Mar 6, 2012 at 6:54 PM, Brian LeRoux <b...@brian.io> wrote:

> bump. my $0.02. we have two choices: relative or protocol handler.
>
> rel means devs have to construct paths from (brittle) strings and
> concatenating ... using app ids, etc. less extensible.
>
> i'd like to push we gun for protocol handlers for app level and root to
> start:
>
> app://
> root://
>
> in the future we could add discovery for things like:
>
> sdcard://
>
>
>
> On Mon, Feb 27, 2012 at 11:39 AM, Filip Maj <fi...@adobe.com> wrote:
> > 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" <si...@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 <fi...@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. :)
> >>>
> >>>
> >
>