-
Type:
Enhancement
-
Resolution: Future Project
-
Priority:
P4
-
None
-
Affects Version/s: 1.4.0
-
Component/s: install
-
sparc
-
solaris_8
The IANA registers all sorts of identifiers and whatnot for use on
the Internet, one of which is the MIME Content-Type values.
Relavent web pages are:
http://www.iana.org/numbers.html#M
http://www.isi.edu/in-notes/iana/assignments/media-types/media-types
The second is linked to from the first, and is the official list
of properly and duly registered MIME types. Note that the word "Java"
appears nowhere on that page.
JWS is intended to be an important and widely spread part of the Internet
infrastructure. It will greatly aid getting JWS accepted if there is
a standard MIME type for it, as that will give clearer notice to
browser manufacturers and various pieces of software what is the content
being returned with a JNLP file is requested. They will have an easier
time getting documentation on what to expect if the JNLP files are
duly registered, as all they have to do is browse the registry and see
where the documentation is located. Note the current situation
where we use an unregistered x- content type.
Content types beginning with X- are supposed to be for experimentation.
JWS is well past the stage of experimentation.
Let us be a proper Internet citizen and actually use the Internet Standards
process that we like to wrap ourselves with.
As an aside - I know there are other Java data types which have
associated MIME types in use, but which are not registered. Note
that the official registry does not list the word "Java" *ANYWHERE*.
The other one I'm aware of is the serialized object, used in RMI
and DnD. An earlier bug, 4028660, asked to register MIME types
and was closed as "Will not fix".
JNLP and serialized objects have different target audiences. JNLP files
are intended to be stored on web servers and loaded to web browsers
through HTTP requests. There's a lot in that path where the software
is developed by third parties. On the other hand, java serialized
objects are primarily used internally to the Java implementation, and
not with software developed by third parties. JNLP files therefore
require a much greater degree of handshaking and coordination with
the rest of the world.
the Internet, one of which is the MIME Content-Type values.
Relavent web pages are:
http://www.iana.org/numbers.html#M
http://www.isi.edu/in-notes/iana/assignments/media-types/media-types
The second is linked to from the first, and is the official list
of properly and duly registered MIME types. Note that the word "Java"
appears nowhere on that page.
JWS is intended to be an important and widely spread part of the Internet
infrastructure. It will greatly aid getting JWS accepted if there is
a standard MIME type for it, as that will give clearer notice to
browser manufacturers and various pieces of software what is the content
being returned with a JNLP file is requested. They will have an easier
time getting documentation on what to expect if the JNLP files are
duly registered, as all they have to do is browse the registry and see
where the documentation is located. Note the current situation
where we use an unregistered x- content type.
Content types beginning with X- are supposed to be for experimentation.
JWS is well past the stage of experimentation.
Let us be a proper Internet citizen and actually use the Internet Standards
process that we like to wrap ourselves with.
As an aside - I know there are other Java data types which have
associated MIME types in use, but which are not registered. Note
that the official registry does not list the word "Java" *ANYWHERE*.
The other one I'm aware of is the serialized object, used in RMI
and DnD. An earlier bug, 4028660, asked to register MIME types
and was closed as "Will not fix".
JNLP and serialized objects have different target audiences. JNLP files
are intended to be stored on web servers and loaded to web browsers
through HTTP requests. There's a lot in that path where the software
is developed by third parties. On the other hand, java serialized
objects are primarily used internally to the Java implementation, and
not with software developed by third parties. JNLP files therefore
require a much greater degree of handshaking and coordination with
the rest of the world.