Do you mean that it is thread-safe to use the same static instance of a Tika object?
Event so, a Tika.get() call like the one I described makes sense. But is Tika really thread-safe in the first place? On Mon, Feb 11, 2013 at 4:14 AM, Nick Burch <[email protected]> wrote: > On Sat, 9 Feb 2013, Public Network Services wrote: > >> The Tika toolkit created via a call to new Tika() seems to do take some >> time to instantiate, so I was wondering whether it would make sense to add >> a get() method in the Tika class and offer instantiation via a ThreadLocal >> variable, for thread-safe operation, in applications that need to >> extensively use the toolkit. >> > > I've got a feeling you can just create one and re-use it. I've certainly > not noticed problems with having a single DefaultParser and single > mimetypes registry across an application > > Nick >
