All -
Here's an idea that, even if accepted, might have to wait a while, but I
wanted to put it out there while it's fresh in my mind.
Tika needs to do MIME type and encoding detection for the purpose of
parsing. I'd like to suggest elevating those services to be explicitly
stated services of Tika, so that we can increase Tika's usefulness to its
users.
In addition, if these could all be exposed in a utility class that allowed
instantiation (1), then an instance of that utility class could be dropped
into a JEXL or other context for use in expressions.
It would be great to tell users that they could create a single instance of
our utility class and have access to parse(), getMimeType(), and
getEncoding() methods. We could still expose our objects, but this would be
an alternate way of accessing them.
- Keith
(1) Although the javadoc for Commons Lang utility classes discourages their
instantiation by saying:
"StringUtils instances should NOT be constructed in standard programming.
Instead, the class should be used as StringUtils.trim(" foo ");"
They have nevertheless decided to provide public constructors, saying:
"This constructor is public to permit tools that require a JavaBean instance
to operate."
--
View this message in context:
http://www.nabble.com/Exposing-MIME-Type-and-Encoding-Detection-tf4636584.html#a13241723
Sent from the Apache Tika - Development mailing list archive at Nabble.com.
