<mailto:[email protected]> www.consil.co.uk <http://www.consil.co.uk/>On 01/07/2012 16:51, Nick Burch wrote: > On Sun, 1 Jul 2012, Jason Judge wrote: >> Am I understanding it correctly that tika-server and tika-app are just two >> examples of the way tika can be used, and are just thrown together as a >> quick-start demo rather than core functionality of the main part of the >> project, which is a collection of libraries and tools to be used by other >> java applications. > > They should be more than a quick-start, but neither are how most people use > Tika. Most Tika users are Java programmers, so call either the Tika facade > class (simple use cases), or the Parser/Detector/etc directly (advanced uses). > > The tika-app has tended to be used for testing and debugging, but is > increasingly also being used for non-Java integrations. The tika server is > quite new, so finding areas where core Tika functionality isn't exposed is to > be expected. The Tika API is pretty simple and easy to use, so it's generally > pretty easy for a (Java) programmer to expose extra bits of it in the app or > server when they have the need. Sadly, this does tend to mean that non Java > users need to raise enhancement requests when they hit things that aren't > exposed.... > > Nick
Thanks Nick. That bit of background helps a lot. Tika is pretty unique across the whole of the open source landscape in terms of its flexibility, wide range of inputs and ease of use. I could see its use expanding into many other areas and platforms to fit a niche. I've already noticed it is used by some PHP applications, such as Knowledge Tree, but they tend to use it as a plugin to solr, with solr providing the API into Tika. So, feature requests, command line, or...learn java. It is going to be a busy Summer :-) -- Jason
