Thanks Bertrand, Robert. I am exploring an approach wherein the Sling webdav servlet would be passed a tika detector via @Reference as suggested . The current SlingTikaDetector would also expose itself as a service and the webdav servlet will get its reference for further use. Alternatively, one can pass another tika detector to the webdav servlet. Sling launchpad already includes a Tika Osgi bundle which provides the default TikaDetector which can be used as an alternative to the internal SlingTikaDetector . I have logged https://issues.apache.org/jira/browse/SLING-4694 to track this.
Regards Satya Deep On Mon, May 4, 2015 at 5:18 PM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > Hi, > > On Mon, May 4, 2015 at 1:36 PM, Satya Deep Maheshwari > <connus...@gmail.com> wrote: > > ...How about modifying the > > existing SlingTikaDetector itself and adding a mechanism in it to resort > to > > inputstream based mime-type detection if name based detection draws a > > null.... > > I don't think we want to make this the default, as that's much more > expensive than the other methods. > > As Robert says, providing an extension point for content-based mime > type detection is good. > > -Bertrand >
