Hi Bruce!
McDonald, Bruce wrote:
> What about your threading issues?
Unresolved, I'm afraid. Because of current deadlines I'm
forced to run single-threaded for a little while, until I
can return to that particular issue. I have read quite a
lot of the code but am unable to find the culprit. I have
seen some other peculiar behaviors related to multithreaded
execution as well, though. E.g sometimes multiple instances
of PipelineStageFactory and/or PipelineStageResolver are
created, depending on timing issues. Those can be resolved
through some synchronizing in selected spots, but they do
point me to believe that there might be more fundamental
issues related to multithreaded execution within Babeldoc
that may require more minds peering inside the code.
Other than that, I'm happy! ;-)
I have one small additional change to the DirectoryScanner
that I needed for my current work: In a late pipeline stage
I need to know where the scanner moved the original scanned
file, in order to move a different, but related, file to the
same location. The change consists of a document attribute,
called "done_dir" which is set by the DirectoryScanner at
the same time as the scan_path and file_name attributes. If
this change is useful I can submit a patch for that too?
I did one more thing, but I just saw that Dejan fixed it:
The file_name problem in the scanner. He beat me to it! :-)
/David
|
