The thing is, the standard JSON representations of data are about as compact as one can get in Java -- unlike XML where the representation is very inefficient. In order to read the JSON you'll create most of the objects used to represent it, so you'll churn through about the same amount of heap whether you hold onto the representation or not -- the only difference is the "high-water-mark", and that's much less critical than "churn" in terms of app performance.
On Dec 26, 4:54 am, ko5tik <[email protected]> wrote: > On Dec 25, 11:51 pm, DanH <[email protected]> wrote: > > > 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. > > In my game I pull up to 1000 highscore entries from server (well,not > always > but certainly on first synchronization) and load them from internal > storage - > there is definitely need in pull parsing. I also utilize my own small > data binding > library, and will add pull parsing to it when i get some time. > Everybody is welcome to join the > effort:https://github.com/ko5tik/jsonserializer -- 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
