Robert et al,
I propose that we add a facility to look up plugins by mime-type (in
addition to looking up by extension).
The existing mechanism works fine for local files. But when accessing data
via a URL (with the CURL plugin or by some other means), it is often the
case that you can only
Hi Glenn,
I'm open to these suggestions, but would prefer to keep the changes to
a minimum in terms of extra code/API.
Could the mime type simply be mapped to a plugin name? If so then all
we'd need to do to set up a alias list for mime type in addition to
the current extension aliasing that
Robert,
I considered that, mapping mime-types to extensions, but shied away from the
idea that adding a plugin might require mime-types hard coded into Registry.
How would you include support for new types, say in a plugin in an external
NodeKit?
Glenn Waldron : Pelican Mapping :
Hi Robert, Glenn,
Could the mime type simply be mapped to a plugin name? If so then all
we'd need to do to set up a alias list for mime type in addition to
the current extension aliasing that the osgDB::Registry holds.
I've seen lately, MediaWiki keeps a mapping of MIME type to extension
HI Glenn + JS,
On Mon, Feb 23, 2009 at 3:00 PM, Jean-Sébastien Guay
jean-sebastien.g...@cm-labs.com wrote:
Hi Robert, Glenn,
Could the mime type simply be mapped to a plugin name? If so then all
we'd need to do to set up a alias list for mime type in addition to
the current extension
On Mon, Feb 23, 2009 at 10:00 AM, Jean-Sébastien Guay
jean-sebastien.g...@cm-labs.com wrote:
Hi Robert, Glenn,
Could the mime type simply be mapped to a plugin name? If so then all
we'd need to do to set up a alias list for mime type in addition to
the current extension aliasing that the
6 matches
Mail list logo
