同步框架 - 技术适合/架构问题 [英] Sync Framework - Technology Fit / Architecture Question

查看:60
本文介绍了同步框架 - 技术适合/架构问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

假设我有一个大型图书馆(> 100,000个对象)的数字资产(音频,视频,图片等)。该图书馆由数字资产管理系统(DAM)管理。 DAM将元数据存储在数字文件和专有数据库中;
SDK可用于获取资产’元数据以及源文件的UNC路径。

Let’s say I have a large library (>100,000 objects) of digital assets (audio, video, images, etc.). The library is managed by a digital asset management system (DAM). The DAM stores the meta-data both in the digital files and a proprietary database; an SDK is available to get the assets’ meta-data as well as the UNC path to the source file.

目标是创建自定义应用程序以允许用户从库中选择资产的子集(通常基于元数据,即项目名称,作者等)并将
单向同步到另一台设备(笔记本电脑,SD卡等) )。问题是,当文件被复制/传输时,它们应该被转换和/或加水印。例如,高质量的音频文件应转换为
到较低的比特率;高清视频应转换为较低的分辨率;高分辨率图像转换为JPEG格式。我知道Sync Framework赢得了转换的帮助,我们需要实现这个。

The goal is to create a custom application to allow the user to select a subset of assets from the library (usually based on meta-data, i.e. project name, author, etc.) and do a one-way sync to another device (laptop, SD card, etc). The catch is that when the files are copied/transferred, they should be converted and/or watermarked. For example, high-quality audio files should be converted to lower-bit rate; HD video should be converted to a lower resolution; high-res images converted to JPEG format. I know the Sync Framework won’t help me with the conversion, this we will need to implement.

我的问题是,有没有办法让Sync Framework拦截转移文件,动态执行转换,并记录本应记录的元数据,就像文件尚未转换一样?通过使用原始文件的
元数据,这将允许将来的同步传递知道不必重新传输(并重新转换)该文件。或者有更好的方法吗?

My question is, is there a way with the Sync Framework to intercept the transfer of the file, perform the conversion on the fly, and record the meta-data that would have been recorded as if the file had not been converted? By using the original file’s meta-data, this would allow future sync passes to know that the file does not have to be re-transferred (and re-converted). Or is there a better way to do this?

通过创建自定义提供程序,这是否正确?如果是这样,它提供了什么附加值来通过自定义(非同步框架)解决方案来复制和隐藏文件?

Is the correct way to do this by creating a custom provider? If so, what additional value does this provide over a custom (non-Sync Framework) solution to copy and covert the files?

推荐答案

是的,您可以在传输文件时执行转换,但仍然更改了元数据,就像文件未转换一样。如果使用KnowledgeSyncProvider或自定义提供程序,当它将数据从源提供程序保存到目标提供程序时,
由提供程序完成 - 同步框架不受影响。您可以让源代码向目的地发送较低保真度的版本。

Yes, you can do the convert while transferring the file and still have metadata changed as if the file was not converted. If using a KnowledgeSyncProvider or Custom Provider, When it come to saving data from the source provider into the destination provider, it is done by the providers - the sync framework gets out of the way. You can have the source send a lower fidelity version to the destination.

看起来您只会进行单向同步,并且不太可能遇到任何冲突,因为目的地不会修改文件 - 是吗?鉴于此,我仍然认为他们的Sync Framework将非常有用,因为更改枚举将更快更有效。

It looks like you will only be doing a one-way sync, and are not likely to encounter any conflicts, since the destination will not modify the files - is that right? Given that, I still think they Sync Framework will be useful, since change enumeration will be faster and more efficient.

 


这篇关于同步框架 - 技术适合/架构问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆