All - A few days ago I posted a patch that would have enabled the use of URL's as input specifiers in Tika (see TIKA-17). However, given the code changes since then, I expect that applying the patch would now fail.
I am willing to do the work to bring this functionality to Tika. There are several ways this could work: * I could submit a single patch that would enable the URL functionality. This would likely touch several files. * I could submit a greater number of patches containing more incremental changes, but for this to be practical, there would have to be a faster turnaround (from submitting the patch to having it applied). * I could send you a tar ball of my code that works, and you could pick what you like to commit out of it. * Or, of course, you could choose not to do any of these. My situation is this -- my project needs to use Tika, and we are willing to use an experimental version whose interfaces will change. We would love it if we could check out a revision number from the Subversion repository. Unless we can get such a copy in a few days, we will have to use a customized version of the source code, which, obviously, we would prefer to avoid. I am more than willing to invest time and energy in this. Tika is an extremely useful product, and it can be functional momentarily without a great deal of change. A side benefit of having it in a functional state (albeit experimentally) is that it could attract input from more developers and users. Please let me know how I can be helpful. Thanks, - Keith -- View this message in context: http://www.nabble.com/Using-URL%27s-for-Input-Resource-Specifiers%3A-How-can-I-help--tf4477197.html#a12766332 Sent from the Apache Tika - Development mailing list archive at Nabble.com.
