serialization - Should iOS app's plist be compressed for optimization purposes? -
the app have under development utilizing lot of plist that's taking lot of space. considering zipping plist files. @ runtime, app unzip them nsdata , deserialize them nsdictionary using nspropertylistserialization eventual use.
is there risky approach? or useless if property list output encoding set binary.
if getting point you're considering zipping property lists save on space, think it's time move different format. property lists storing few defaults or settings, they're not replacement database.
my recommendation @ moving data core data database. if trying embed large digital files elements in property list, @ storing separate resources in application bundle or in application's /documents directory.
core data allow lazy-load items need them, saving on load times , memory, , sqlite base provide fast read / write times.
Comments
Post a Comment