> Funly enough, I was thinking the other way around: could it be a > requirement for someone that two plugins parse the same content-type? > One plugin does some parts of the parsing, then hands over the page to > another one, _à la_ Visitor.
It could be an interesting feature. But for now, I concentrate on needed features, and as you show it, there's many issues to solve: - I looked quite briefly at the current code, so I could be wrong, but > the parsers are put into cache (in ParserFactory) in a Hashtable which > takes <content-type>+<extension> as a key. One of the plugins will > overshadow the other, most likely the one which loaded last. That > being said, we can end up in strange situations were a plugin handles > pps whilst another one handles ppt. > - Also, the way it now works, a plugin does the job on its own. But if > two plugins were to do the parsing, wouldn't be the results deduped at > some point anyway? > - Last thing, I couldn't think of any convincing example. Jérôme -- http://motrech.free.fr/ http://www.frutch.org/
