We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There's no attempt or tests for thread safety yet.
PDF now has early support for multi-threaded page construction.
This library could possibly support thread-safe fragments that can be composed concurrently for final sequential assembly, along with the pages.
The text was updated successfully, but these errors were encountered:
wip on threading #10
1eabfb5
adding fragments. no attempt to make them thread-safe. t/threads.t currently failing in various ways.
In place with PDF::Tags release 0.1.2. A bit more testing/use in the field needed.
Sorry, something went wrong.
Sort of working, however t/threads.t currently produces an unstable /ParentTree ordering and /StructParents links back to the parent tree.
t/threads.t
/ParentTree
/StructParents
Ideally, this should be stable, if this can be achieved without significant concurrency bottleneck.
We'd need to somehow defer final construction of these for final sequential allocation.
No branches or pull requests
There's no attempt or tests for thread safety yet.
PDF now has early support for multi-threaded page construction.
This library could possibly support thread-safe fragments that can be composed concurrently for final sequential assembly, along with the pages.
The text was updated successfully, but these errors were encountered: