Storing large (e.g. image/movie) files in Core Data on the iPhone -


Seeing Apple iPhone Core Data Recipes sample app, they store image files in main data objects, It usually does not seem to be intelligent. Now I also capture the stories on the 3GS. The question is: Is it wise to store images in core data on iPhone, and besides, movies?

Additionally, in addition to loading in memory, apparently the design used in dishes (i.e., accumulating the image in a different model) allows "defect" of core data ( Which seems to mean lazy loading), but I'm not sure it's really true.

Look here: It seems that normal coco advice is to use different files ....

It depends on whether the coreadata is more than capable of accumulating large blobs with good performance. There are large groups:

  1. If those blobs are the properties of those entities that can not always be faulty in you, then it is necessary to take caution in order to ensure that whenever you Use what you tell the CD that the qualities are not faulted unless you ask that you can work apart from the blops in your own organizations, which unless you use it through a relationship Will not blame the child.
  2. Your continuous store is a monolithic file, which means that this change needs to be copied during backup

    The first issue is usually not a big deal, It usually takes for the phone, while it is synching with iTunes because it takes time for backups, you just need to be careful second is no issue, if the data is effectively read only , But if you have it Two hundred megabytes of data to store, it's pretty awesome user experience.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -