> Jérôme Charron wrote: > > I really don't like this solution to centralize this kind of > informations. > > I think, it's the plugin responsability to claim the > > content-type/path-suffix it can handle. > > However, what happens if more than one plugin claims that it can handle > any given content-type? E.g. html parser may claim that it supports > plaintext. but there is another plugin specifically for plaintext. Which > of them wins?
That's the drawback of this solution (randomly choose a plugin if many claims to handle a content-type) The drawback of the "centralized" one is to give to the administrator the ability to easily associate parse-plugin to a content-type this one doesn't handle. Jérôme -- http://motrech.free.fr/ http://www.frutch.org/
