In that scenario, you are supposed to start a new thread in which the
copying proceeds. Factor's IO is implemented as a blocking facade
around an asynchronous core. That's why the CopyFile call on Windows
is likely a bug, it is blocking for real. See this thread:
https://sourceforge.net/p/factor/mailman/message/32588643/

I also wonder if you are not working on a to low level for the
feature. The io backend hooks are mostly for encapsulating platform
differences and are hard to extend.


2016-06-15 0:18 GMT+02:00 Alexander Ilin <ajs...@yandex.ru>:
> But there is still a point in having a separate batch-processing backend.
> You see, if you start a copy operation in the Listener interactively, then
> even with the good variant of the copy-file you won't be able to continue
> working with the Listener until the copying is finished. Sure, it won't
> hang, and the caret will keep blinking, but you won't be able to queue the
> next file to be copied while the first one is still being handled. That's
> what my custom backend would do for you.


--
mvh/best regards Björn Lindqvist

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk

Reply via email to