Administrator unwilling to set MIME type
Heather Kelly
Hi,
I have recently started using a new plug-in made by FutureWave Software.
This plug-in is new, but fast becoming popular. In order for it to work
in Netscape, the MIME type must be set correctly on the server software.
Since administrator rights are required, I have asked CSC WWW Maintainer
to do this. However, the response from the Maintainer was that the
plug-in is experimental and non-standard, and therefore they were
unwilling to set it. I do not understand this reasoning, especially
since the plug-in has been incorporated into Microsoft's Site
(http://www.msn.com) and everyone that visits the site must download the
plug-in if using Netscape.
Following is the MIME type information:
Server Setup Requirements (All Servers)
MIME Type: application/futuresplash
Suffix: .spl
According to the CSC WWW Maintainer, "The problem is that you want
"application/futuresplash", which would be an official MIME type, as
opposed to "application/x-futuresplash", which would mean that it's
experimental and nonstandard." Does anyone understand this?
It was further suggested that I try using the .htaccess file to
accomplish the same goal. However, I do not what the .htaccess file is
let alone how to use it to solve my problem. Does anyone have any
suggestions?
Finally, I do not understand why the administrator is unwilling to set
this MIME type. The web is progressive, not static. The technology is
constantly changing and we should be willing and able to progress and
evolve.
Sean Kubin
Blake Winton
In article <3295AF...@calum.uwaterloo.ca>, heat...@compusmart.ab.ca wrote:
I'm sure you didn't mean for this to sound as much like a troll as it
did...
>I have recently started using a new plug-in made by FutureWave Software.
>This plug-in is new, but fast becoming popular.
Popularity never won anything points in the CSC... (as far as I know,
anyways... :)
>In order for it to work
>in Netscape, the MIME type must be set correctly on the server software.
This is rarely true... You can also set the mime type on the client.
>Since administrator rights are required, I have asked CSC WWW Maintainer
>to do this. However, the response from the Maintainer was that the
>plug-in is experimental and non-standard, and therefore they were
>unwilling to set it.
Sounds fair enough to me so far...
>I do not understand this reasoning, especially
>since the plug-in has been incorporated into Microsoft's Site
>(http://www.msn.com) and everyone that visits the site must download the
>plug-in if using Netscape.
Ah, and the CSC is a pro-Micro$loth organization? I think not. By
involing the name of the mighty demon "Bill", you are ensuring that
more and more people will flock to the opposing team.
>According to the CSC WWW Maintainer, "The problem is that you want
>"application/futuresplash", which would be an official MIME type, as
>opposed to "application/x-futuresplash", which would mean that it's
>experimental and nonstandard." Does anyone understand this?
Yes. There is a group of people who determine what the mime types
should be. Anything without an "x-" is officially sanctioned by them.
Since they have not decided to support the futuresplash type at this
point, the mime type "application/futuresplash" is wrong. It implies
that the group has given their consent to something which they have not.
If this doesn't bother you, then I will bring your name up in all
of my future posts, and attribute ludicrously fascist and demeaning
statements to you.
>It was further suggested that I try using the .htaccess file to
>accomplish the same goal. However, I do not what the .htaccess file is
>let alone how to use it to solve my problem. Does anyone have any
>suggestions?
Then read some manuals. If you're connecting with Windows 95 (as I
assume you are, since most of the new plug-ins aren't supported on
Unix), then you just need to add it into your "file types". (Do a help
on "File Types" if you don't know what they are).
>Finally, I do not understand why the administrator is unwilling to set
>this MIME type. The web is progressive, not static. The technology is
>constantly changing and we should be willing and able to progress and
>evolve.
On the other hand, the web has grown into a splintered chaos of
flash and glitter with no content. There are millions of home pages
which look like crap, unless you're using Browser X, with plug-in Y, on
machine Z, with W meg of ram, and a screen size of V by U by T million
colours. The web, although progressive, has reached the point of
saturation, because any new content (of which there is precious little),
will be unable to be read, except by a select few. There needs to be
some order, or it will be overgrown (if it isn't already).
Since this plug-in is experimental, and unsupported on all but a few
platforms, and attempting to circumvent the proper channels, and going
to be replaced in a few months anyways, I fully support the
administrator's decision to stop the chaos. (Wow, you don't often hear
me say _that_... :)
Blake.