Sure. I created this issue because I saw in ParserFactory support for Files and Strings (filespecs) but not URL's. Since URL's are the most inclusive resource specifiers, I thought they should have a stature at least as high as the alternatives.
I see your point and agree with you that Parsers should only need to know about streams. Anything else used to manage the streams should be outside of them. - Keith JIRA [EMAIL PROTECTED] wrote: > > > [ > https://issues.apache.org/jira/browse/TIKA-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529163 > ] > > Jukka Zitting commented on TIKA-17: > ----------------------------------- > > Couldn't you achieve the same functionality with an adapter class that > takes a content URL > (or a set of URLs for content, config, etc.), opens streams for accessing > the identified resources, > and passes the streams to the core stream-based parser framework? > >> Need to support URL's for input resources. >> ------------------------------------------ >> >> Key: TIKA-17 >> URL: https://issues.apache.org/jira/browse/TIKA-17 >> Project: Tika >> Issue Type: Improvement >> Components: general >> Affects Versions: 0.1-incubator >> Reporter: Keith R. Bennett >> Assignee: Chris A. Mattmann >> Fix For: 0.1-incubator >> >> Attachments: tika-17-2.patch, tika-17.patch >> >> >> It would be extremely helpful to support URL's instead of just File's for >> input resources. This would enable us to use class loaders to find >> resources, and in general support resources that are not available via >> the filesystem. >> Patch coming... > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > > -- View this message in context: http://www.nabble.com/-jira--Created%3A-%28TIKA-17%29-Need-to-support-URL%27s-for-input-resources.-tf4438398.html#a12802324 Sent from the Apache Tika - Development mailing list archive at Nabble.com.
