Michael Kaply wrote: > We need a way to map some default mime types to extensions in OS/2, > similar to a mime.types file on Linux or the registry on Windows. > > We have a couple ways to do this, and I need some opinions. > > 1. Actually use a mime.types files. This would be a text based file that > stored the extensions. The location of the file would be specified as a > preference. > > 2. Create an INI file in OS/2 (like MIMETYPE.INI or something silly) > that stored extension to mime type mappings. > > 3. Create a Mime Types entry in OS/2 ini that had all the extensions and > a corresponding mime type. > > Note that options 1 and 3 only store extension to mime type mapping > whereas number 2 could actually store additional info like a default > application to start the mime type with. > > What do people think is best? > > Thanks > > Mike Kaply > IBM >
I choose none of the above. We need that really long default listing of mime types like 2.02 had. Store the mime type of each item in its EA type data, if the mime item is to be persistent. Use the ini to store the mime type to application mapping. Don't use extensions as there are many different mime types using the same extension. Place the ini in the same folder as the exe. Remember that when the item is received/sent, its mime type is declared in the header, not in the extension. -- Bill <Have a Good April Fool's Day>
