Lol Fabrice, I know what you are saying. But Library != api We already have the api. What I understand (correct me if I am wrong ) that Thinker doesnt want to use the sessionStorage and/or LocalStorage apis, neither wants to manage the variables directly. He wants something in between that does it automatically. Which already have the logic to restore when the app crashes. So, what I am suggesting is use a Library that does that, instead of an api. Secondly, every app might not want to do it, so we can limit the library to a single app, instead of calling it for every app in system api.
But then again, we need to respect what Thinker requires for his project as well. He might be doing something where he might require it for every app. Thats why I want hear his reasoning for adding an api instead of a library call. *Prateek Jadhwani* www.prateekjadhwani.com On Thu, Mar 27, 2014 at 6:57 PM, Fabrice Desré <[email protected]> wrote: > On 03/27/2014 03:51 PM, Prateek Jadhwani wrote: > > Thinker, > > > > I would suggest making a library to do all that, and do all that stuff. > > I mean on the Gaia end, rather than going for B2G. And then, this > > library could be used by system app to do what you want to do. > > > > I would like to know your reasoning for creating an api in B2G rather > > than Gaia. Because I do agree with with Fabrice, creating an api just > > for this task might not be the proper way to achieve this goal. It might > > be a way, but not a proper one. > > Note that I'm not advocating for a gaia side solution. That would > probably not perform as well as the session restore we build in gecko. I > just said that I'm not convinced if we need any api at all. > > Fabrice > -- > Fabrice Desré > b2g team > Mozilla Corporation >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
