Google Gears - 支持什么级别的同步？
我有几个关于数据同步的问题。 架构 对此似乎不太清楚：
Google Gears 是否提供自动同步数据 （从客户端到服务器以及服务器到客户端）？
如果它确实提供了自动数据同步功能，那么我可以吗？ 编写函数来挂钩同步机制（在服务器上和在 客户端）来控制同步哪些数据？
有办法对服务器上的数据进行分区吗？ 例如一个 客户端应该能够只下载表中的那些行 与之相关（例如表中有“主机名”列， 并且只有那些包含尝试访问的客户端主机名的行 下载数据应该下载到里面）
基本上我正在寻找的是：Google Gears Synchronization 支持SQL Server Merge等数据同步功能 复制？ [ http://technet.microsoft.com/en-us/library/ms152746 .aspx]
I have a few questions about data synchronization. The architecture
does not seem to be clear about this:
Does Google Gears provide from automatic synchronization of data
(from client to server and server to client)?If it does provide for automatic data synchronization, then can i
write functions to hook into the sync mechanism (on the server and on
the client) to control what data is synced?Is there anyway to partition the data on the server? for example a
client should be able to download only those rows in a table which are
related to it (for example there is 'hostname' column in the table,
and only those rows which contain the hostname of the client trying to
download the data should be downloaded to it)
Basically what I am looking for is: does Google Gears Synchronization
support the data synchronization features like SQL Server Merge
replication?
[ http://technet.microsoft.com/en-us/library/ms152746.aspx ]
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
Gears 不提供任何同步功能。 我记得我记得在 Gears 刚推出时听过一个播客采访，采访了一位 Gears 开发人员，他说他们想提供一个框架来帮助同步，但意识到每个人的同步需求都有很大的不同，以至于太差了。很难找到一种一刀切的解决方案。
此外，需要注意的是，由于 Gears 的数据库部分实际上只是一个可通过 javascript 访问的客户端数据库，因此 Gears 中没有任何内容指定特定的服务器端实现，甚至特定的服务器 API。 因此，执行您所描述的数据分区之类的操作取决于开发人员，就像与服务器交互一样。
Gears does not provide any synchronization capabilities. I think I remember listening to a podcast interview with one of the gears developers when it first came out, and he said that they wanted to provide a framework to help with synchronization, but realized that everyone's synchronization needs were sufficiently different that it would be too difficult to find a one-size-fits-all solution.
In addition, it's important to note that because the database portion of Gears is really just a client-side database accessible from javascript, there's nothing in Gears that specifies a specific server-side implementation, or even a specific server api. Thus, doing things like the data partitioning you describe are up to the developer, as is interfacing with the server in general.
是的，您可以根据需要对服务器上的数据进行分区...因为没有自动同步
Yes, you can partition the data on the server however you want... because there's no automatic synchronization
如果您查看 Google Gears 文档，您会发现本地 SQLite 数据库不可写。 它对于 Gears 是可写的，因此它甚至无法帮助您本地缓存将发送到服务器的数据。 此时它用于缓存只读数据。
If you look at the Google Gears docs you'll see that the local SQLite database is not writable for you. It's writable for Gears, so it can't even help you with local caching of data that will be sent to the server. It's for caching read-only data, at this point.