在服务器上保存核心数据实体
如何在服务器上保存核心数据实体？
如果手机创建了核心数据对象，那么它们发送到服务器后如何保存？
将数据发送到服务器并让服务器保存核心数据对象是不是更有效率？
How would one save core data entities on a server?
If a phone creates the core data objects, how can they be saved if sent to the server?
Is it more efficient to send the data to the server and have the server save the core data objects?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
尝试 RESTKit
Try RESTKit
这并不是当今核心数据的真正特征。核心数据主要是一个对象图层，可以持久保存到永久存储（例如 xml 或 sqlite）。这些对象（NSManagedObject 的实例）仅在创建它们的上下文中有效（它们甚至不是线程安全的）。
要将对象发送到另一台服务器，您必须序列化该对象，将其打包以便传输到您的服务器，然后在服务器端反序列化对象（尽管它们实际上不会是同一对象的实例，您只需复制与您的应用程序相关的重要属性）。
为了使服务器上的对象进入某种有用状态，您很可能必须在服务器上下文中创建新的实体实例。
从我的角度来看，除非 Apple 为 Core Data 提供了一些类似 CORBA 的行为，否则我根本看不到这样做的好处。我会把线程安全的 NSManagedObject 放在更高的位置（不必参与在线程之间传递 objectID）。
That's not really a feature of core data as it exists today. Core data is primarly a object graph layer that can persist to permanent storage (such as xml or sqlite). The objects (instances of NSManagedObject) are only valid within the context that they are created in (they are not even thread safe).
To send the objects to another server would invole you having to serialize the object, package it up for transmittion to your server, and then de-serialize the objects on your server side (they really wouldn't be instances of the same object though, you would just be coppying over the important properties that are relevant to your application).
To get the objects into some kind of userful state on your server you would most likely have to create new Entity instances in your server context.
From my perspective, I can't see the advantage of this at all unless some CORBA like behaviour was provided by Apple for Core Data in general. And I'd put thread safe NSManagedObject's up higher than that (whithout having to get involved in passing objectID's around between threads).