file name extensions

[Greg Titus]

>> Any suggestions on how to get OmniWeb to handle our own weird
>> extensions... for example, we want to use WWW/OmniWeb as a front  
>> end to our internal help system.
> Indeed! Suuporting explicit MIME type settings instead of a simple 
> "open" is a feature that a professional web browser must have.

Our internal version now supports setting up custom mappings of  
MIME types to file extensions, and handles content encodings the  
same way. I'm still working on decoding the content-encoding for  
types that are presented, so that compressed html and compressed  
inline images will work. I'm not sure when we'll release 0.9.4, but  
it should be in by then.

Note that this is doing the first half of the job - the Workspace  
still does the second half. For example, if you download a file  
named "foo" that has a content type of  
"application/x-our-internal-help" and content encoding of  
"compress", you can set up a mapping for  
"application/x-our-internal-help" to "o_i_h" and OmniWeb will write  
out and ask the Workspace to open a file called "foo.o_i_h.Z". You  
still have to have Opener around to open up .Z files, and have your  
app registered with the Workspace to open .o_i_h files.

(This kind of content-type to extension to application mapping is  
exactly what most other decent browsers do, except they generally  
have to take on Workspace's job themselves...)

	-Greg

---------------------
Greg Titus
Omni Development Inc.
toon at omnigroup.com