Until you get up to **at least** 10K of JSON (maybe 1M, depending on the overall app size) there's no point in worrying about pull parsing. Reading and parsing the entire JSON file at once will increase temporarily the amount of heap used, but it's hardly a blip in most environments.
On Dec 25, 11:14 am, JP <[email protected]> wrote: > Pull parsing is absolutely a favorite in mobile. While I agree with > Jake, one thing to consider is a fundamental conceptual decision that > is "baked" into the question whether to employ a tree parser or a > streaming parser. Typically, this cannot be optimized away later, and > may drive a fundamental overhaul (refactorization) of the app. > > In my experience, parsing non trivial data streams (JSON, XML, others) > in a mobile environment needs to have the following characteristics: > 1. Maintains a small memory footprint, as mentioned > 2. Allows to immediately draw data as the parser moves along. This is > important due to the often slow connections - it keeps users > entertained (this falls into the "subjective user satisfaction" > category) and informed > 3. Can be instantly stopped at any point. When users start seeing the > data unfold (see 2.), users may want to stop the potentially long data > pull. The app needs to be able to respond to this request on the spot > > On Dec 25, 7:37 am, ko5tik <[email protected]> wrote: > > > Built in JSON is adequate, but as every DOM-Kind of parser pretty > > memory consuming. > > Pull-Parser is really necessary. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
