On Fri, Sep 2, 2011 at 7:25 AM, TreKing <[email protected]> wrote: > On Fri, Sep 2, 2011 at 1:53 AM, LiTTle <[email protected]> wrote: >> >> It is really big xml to load to memory and also it is harder to maintain >> the data! > > Use pull parser to skip to the parts you need or probably better, use a > database if your set is so large and you need to randomly look stuff up.
Agreed, 10,000 shops should never have implemented as string-array resources in the first place. At that volume, you're teetering on the edge of what I'd consider safe to try just holding in some massive in-memory data structure -- if the roster of shops will grow, a database is almost assuredly the right answer. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training...At Your Office: http://commonsware.com/training -- 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
