diff options
| author | Robin Watts <robin.watts@artifex.com> | 2012-03-16 13:44:58 +0000 |
|---|---|---|
| committer | Robin Watts <robin.watts@artifex.com> | 2012-03-16 13:44:58 +0000 |
| commit | a2a62c4110a6bb15470e903b7bd73c7a8ff9cef6 (patch) | |
| tree | 1dd76c4cf950e205e266399ffc89f653f799e53c /doc | |
| parent | b94a2b118585f3dd34a8f3982fde5a91ef698005 (diff) | |
| download | mupdf-a2a62c4110a6bb15470e903b7bd73c7a8ff9cef6.tar.xz | |
Update multi-threaded documentation in light of bug 692925.
State that contexts are baked into devices, and devices used with
document should share the same context.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/overview.txt | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/doc/overview.txt b/doc/overview.txt index 65fe776b..a0074b77 100644 --- a/doc/overview.txt +++ b/doc/overview.txt @@ -214,9 +214,18 @@ multi-threaded operations run smoothly: All subsequent accesses to the document implicitly use the same context; this means that only 1 thread can ever be accessing the document at once. This does not mean that the document can - only be used from one thread ever, though in many cases this + only ever be used from one thread, though in many cases this is the simplest structure overall. +3) "Any device is bound to the context with which it is created." + + All subsequent uses of a device implicitly use the context with + which it was created; this means that if a device is used with + a document, it should be created with the same context as that + document was. This does not mean that the device can only ever + be used from one thread, though in many cases this is the + simplest structure overall. + So, how does a multi-threaded example differ from a non-multithreaded one? |