On Apr 4, 2016, at 17:41 , Gerriet M. Denkmann <gerr...@mdenkmann.de> wrote: > > What are the alternatives?
What I had in mind is that you would construct a composite NSData object that contained the results of compressing each file’s content as sub-components. By compressing this yourself, you could (for example) choose a more aggressive compression technique, or one that’s optimized for the patterns in your data, perhaps, at the expense of processing time, since you’re trying to minimized OTA transmission times. If the package format is only one level deep, then you just need to identify each sub-component (by index or by name, depending on how flexible the internal structure is). If there are multiple levels, you’ll need to describe the relationships as a tree structure. Either way, it’s basically a handful of file name strings. That puts you in control of how much data you transfer. There’s only a handful of lines of code involved here, I suspect. NSFileWrapper.serializedRepresentation does this for you, but I suspect the internal structure is described as NSURLs, and they’re bigger than plain strings, since they can carry additional information such as security scopes. As Graham suggested, some of this may be irrelevant to the iOS platform, but that’s the price you pay using the convenience method. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
