I don't think there's a need for a separate content-type - web servers
will deliver the content with the HTTP headers:
Content-type: world/vrml
Content-encoding: gzip
If you're building a VRML browser which will use HTTP, you can check out the
semantics behind this at the newly-released HTTP draft spec,
<URL:ftp://ds.internic.net/internet-drafts/draft-ietf-http-v10-spec-00.txt>,
particularly sections 7.1 and 8.4. Most servers support Content-encoding, as
far as I'm aware.
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
[email protected] [email protected] http://www.hotwired.com/Staff/brian/