C# FileSystemWatcher 和 FTP
我通过文件系统观察器监视在 ftp 上删除的文件,然后移动到另一个目录。 现在我触发文件系统观察程序的创建事件的复制,但显然在 ftp 的情况下,创建只是一个存根文件,数据会进入并在上传时填充文件直至完成。 任何人对此都有一个优雅的解决方案,或者我必须做我认为我必须做的事情
1 wait till last access time is about n ms in past before I copy
2 throw a control file in there to state that that file is done being copied, then delete control file
3 pound the crap out of it
I monitor files that are dropped on a ftp via filesystem watcher then move to another dir. Now I trigger the copy off the create event of the filesystem watcher but obviously in the case of ftp the create is just a stub file and the data comes in and fills the file as it uploads till complete. Anyone have an elegant solution for this, or do I have to do what I think I have to do
1 wait till last access time is about n ms in past before I copy
2 throw a control file in there to state that that file is done being copied, then delete control file
3 pound the crap out of it
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(6)
这是一个非常幼稚的实现,但它适合我的目的,我在网上看到了足够多的人遇到这个问题,所以决定做出贡献。 该实现是针对我的需求的,鉴于我的问题的性质,我几乎完全不关心更改的事件,但如果人们需要做一些不同的事情,他们可以将自己的代码放入其中,这确实是导致最多问题的创建。 我还没有完全测试过这个,但乍一看它看起来不错
this is a very naive implementation but it suits my purposes, i have seen enough people with this problem on the web so decided to contribute. The implementation is fairly specific to my needs I almost completely unconcerned with changed events given the nature of my problem but people can throw their own code in there if they need to do something different, it really the created which cause the most issues. I havent fully tested this but at first write it looks good
等到您可以独占方式打开文件 - 我不会说这是一个很好的解决方案,但可能是这种情况下最安全的策略。
Wait until you can exclusively open the file- I wouldn't go as far to say that it is a nice solution, but probably the safest strategy in the circumstances.
这是保持同步的实现
here's an implementation to keep in sync
当使用 FTP 从另一台服务器复制文件时,在完成文件复制之前,文件名将使用额外的扩展名(如 .TMP)重命名,如下面的路径示例所示。
C:\InterfaceServer\OilAndGas\XMLForTest\TestStbFile.xml.TMP
要克服这种情况,请执行以下两个步骤
参数包含附加了额外文件扩展名的文件名
文件名,因为它刚刚到达文件夹且尚未完成
与复制操作。
您只需调用以下方法即可删除多余的扩展名
并在代码中添加等待2秒,以便完整的文件
创建后,您可以使用它进行进一步处理。
When file gets copied from another server using FTP, before complete file copy , file name gets renamed with extra extension like .TMP as shown in path example below.
C:\InterfaceServer\OilAndGas\XMLForTest\TestStbFile.xml.TMP
To overcome this situation follow two steps
parameter contains file name with appended extra file extension to
the file name as it just arrived in the folder and not completed
with copy operation.
You need to just call the below method to remove the extra extension
and add wait for 2 seconds in the code so that the complete file
gets created and you can use it for further processing.
让源在数据文件完成后直接上传存根文件,并让 FileSystemWatcher 监视存根文件。 例如,如果数据文件名是 mydata_01234,则存根将为 mydata_01234_stub。 FileSystemWatcher 应该有一个掩码“*_stub”。 然后,您可以通过去掉“_stub”后缀来了解数据文件名。 并且存根文件只有在数据文件完成后才能上传,因此数据文件将是免费的。
如果每个存根文件只有一个字节,那么您应该能够在对数据文件执行任何操作后删除它们,而不会出现问题。 如果您的操作特别快,请在删除存根之前添加 100 毫秒的睡眠时间。
Have the source upload a stub file directly after the data file completes, and have your FileSystemWatcher watch for the stub file. For example, if the data file name is mydata_01234 then the stub woulb be mydata_01234_stub. The FileSystemWatcher should then have a mask of "*_stub". You then know the data file name by stripping off the "_stub" suffix. And the stub file cannot be uploaded until after the data file completes, so the data file will be free.
If the stub files are just one byte each you should be able to remove them after whatever operation you're performing with the data file without issue. If your operations are particularly fast, add a 100 ms sleep before deleting the stub.
4 年后......
存根文件是一个好主意,但是,可能稍微更可靠的方法是让您的源首先创建一个存根文件,上传您的“真实”文件,然后删除存根。
4 years later....
the stub file is a good idea, but, probably a slightly more robust way to do it is to have your source create a stub file first, upload your "real" file, then delete the stub.