ios - Downloading images directly from Parse.com, as opposed to using their API -


i noticed pffile type object stored on parse.com developer account, link open , accessible view/download.

example pffile object named, name.jpg, representing image url :

http://files.parsetfss.com/<some garbled class uuid>/<some garbled image uuid>-name.jpg  <some garbled class uuid> appears same name.jpg, stored on class  , <some garbled image uuid>-name.jpg appears unique uuid's appended actual object name 'name.jpg' 

using above url, anyone/any client can download object

so have questions regarding this:

  1. is normal? design?
  2. will url object change, if nothing else changes?
  3. am being unwise in using information download images directly, thereby saving cost of 1 api call parse (although think i'll make 1 api call anyways url) ?
  4. will downloading directly url, perform better/acceptable compared downloading via parse.com api

yes it's normal. protection via object, don't give access shouldn't have it.

no url shouldn't change, though strictly should query file object each time want sure.

you should care more network calls api calls in general. use cloud code aggregate responses, or batch requests, doesn't reduce api calls.

the download unchanged you're downloading same file same link no matter api use it.


Comments

Popular posts from this blog

authentication - Mongodb revoke acccess to connect test database -

r - Update two sets of radiobuttons reactively - shiny -

ios - Realm over CoreData should I use NSFetchedResultController or a Dictionary? -