Hi Guys, I'd say Jason your comments are well taken, and Nick's replies are spot on.
I got involved with tika-server after Maxim Valyanskiy built a simple JAX-RS layer in his $dayjob and was willing to contribute it back in TIKA-593. His original contribution used the Jersey JAX-RS libraries and I was keenly interested in converting it to use Apache CXF since I had such a great experience with CXF on the Apache OODT project using it to expose our data curation web services. So, I spent a lot of time some months back trying to get this working, with Maxim Valyanskiy and with Sergey Beryozkin who lent a hand from the CXF project. My interest was getting the tika-server module working in my own environment, and documenting what *was* there and less on putting on my architecture hat, and trying to line up things and improve the APIs to make them more consistent with tika-app. That is not to say that we don't want to do that, but just saying that I don't think it's been done yet. Jason: If you'd like to help us propose something that helps us get more consistent from your perspective as a newcomer to the project, we would love to hear your ideas! Cheers, Chris On Jul 1, 2012, at 8:51 AM, 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 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
