On Oct 17, 2013, at 9:19 AM, Brad Gibbs <bradgi...@mac.com> wrote: > As for large data sets, that’s part of the beauty of the NSIncrementalStore > approach. In its purest form, the full data set wouldn’t exist on any one > user’s device. Instead, NSIncrementalStore would fetch the data requested by > the user from the server, as needed, by firing faults. If NSIncrementalStore > worked as advertised, there would be no need to persist the entire data set > to a user’s device.
Which works fine as long as users have always-on connectivity, with reasonably good bandwidth & latency, and the data they need to work with is not too huge. That's not to pick on you or the particular solution, just to point out that one reason that there is not a single good solution in this space is that there is no one-size-fits-all solution simply because there are too many variables to allow that. > I think there’s a huge need for something like this in SMB. Agreed. Probably assuming always-on connectivity, since people usually have 3G or 4G. Do a decent job with managing bandwidth demands and controlling the number of requests/responses, and in cases where the bandwidth/latency is not good enough for a decent user experience, oh well... -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice _______________________________________________ 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
