[Poppler-bugs] [Bug 50992] library should be thread-safe

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=50992

--- Comment #31 from Thomas Freitag <Thomas.Freitag at alfa.de> 2012-08-06 10:15:35 UTC ---
(In reply to comment #30)
> (In reply to comment #24)
> 
> > 
> > Well, i understand that having rendering work is great, but if we are going to
> > make it thread-safe it should be really thread-safe everywhere, i.e. can i ask
> > for the fonts of the document while it's rendering? That's the typical use case
> > were okular now blocks
> 
> Exactly, and the reason why Evince uses a single worker thread.

Sorry, but I fear that "it should be really thread-safe everywhere" is the
wrong statement: It's thread safe is always a question of design, a function or
a method can be thread-safe in the meaning that it can be called / used in
different threads simultaneous or a c++ object can be thread-safe in the
meaning that it can shared in different threads.
So You first need to determine which objects / methods should be shared. So
once again it looks like as if we miss a documentation which is internal and
what is external, external calls should then be thread-safe!

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.