问题描述
在我们的项目中，我们需要能够同时实施：基于文件的同步和基于服务的同步。 它旨在用于启用
连接或禁用/不允许的环境。禁用时我们应该能够交换文件（便携式媒体：usb内存，CD等）
同步也应该是双向的，尽管在每个方向上流动的数据都是独立的，这意味着冲突解决问题不在桌面上。
客户端数据存储可以是XML或SQL Server CE。在服务器端，我们将使用MS SQL Server 2008.
从理论上思考，我们需要的是：包含更改的格式化文档，（de）两侧的序列化程序（客户端和服务器）和交付服务。 （解）序列化器应该能够消费/生成文件和交付服务，如果
要么联系我们的基于Web的服务，要么在可用媒体上准备文件 - 具体取决于场景。
如果你对SyncFx如何帮助有所了解，请感谢如果连接被禁用/不允许。
谢谢！
PS
我们使用的是sql之前的服务器合并复制，但因为订户和分销商都必须在线才能进行同步而不是一个选项。
一切皆有可能
Hi,
In our project we need to be able to implement both: file-based and service-based synchronization. It is intended to be used in environments whereconnectivity is enabled or DISABLED/NOT ALLOWED. When it is disabled we should be able to exchange files (portable media: usb memory, CD etc)
The synchronization should also be bi-directional, although the data flowing in every direction is independent which means that conflict resolution problem is off the table.
The client data storage can be XML or SQL Server CE. On the server side we will use MS SQL Server 2008.
Theoretically thinking, what we need is: formatted document(s) containing changes, (de-)serializers on both sides (client and server) and a delivery service. The (de-)serializers should be able to consume/produce documents and delivery service should either contact our web-based service or prepare files on available media - depending on the scenario.
I understand we can build a very nice home made wheel and believe that is possible on WCF, but am trying to avoid that.
Appreciate if you shed some light on how SyncFx could help in case when connectivity is disabled/not allowed.
Thank you!
P.S.
We used sql server merge replication before, but because both, subscriber and distributor have to be online to do a sync that is not an option.
Everything is possible
这篇关于“从不在线”/始终“离线”/断开连接的客户端的同步的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！