Re: SPEC: DNS conventions & "naming" of VRML sites

Brian Behlendorf ([email protected])
Wed, 14 Jun 1995 12:11:55 -0700 (PDT)

On Wed, 14 Jun 1995, Anthropohedron wrote:
> This requires, of course, that the browser send a HTTP_ACCEPT string.
> Netscape seems to send "*/*, im/gif, im/x-xbitmap, im/jpeg" as its
> string, which is entirely useli> . es"sumaly everything that is defined in
> whatever mailcap is used should be what is sent as the HTTP_ACCEPT.

True, though there are some other subtleties (the spec has wording like
"unusual data types", q values are important, etc.). Ah, to pine for a
generic HTTP module (i.e., HTTP.DLL) that network applications could
share, th> wheel.

> Finally, I think the whole thing will be simplified by merging some HTML
> browser with some VRML browser. I think that inlined VRML would suit
> everyone a lot better than either of these MIME-based solution . Is anyone
> planning to integrate VRML into a WWW browser? Does anyone else believe, as
> I do, that VRML is/should be a primary format, like GIF, JPEG, HTML, XBM,
> and plaintext, not a secondary format like audio and animation?

It would be nice, but how long until some of these swiss-army-knife browsers
literally explode? When I heard that NetScape was planning to implement
Macromedia Director into their browser, on top of PDF and Java, I thought
"well, there's an engineering challenge!".

Ideally, yes, everything could be done within the browser. But I'd
rather see things work the other way, pushing the browser into the OS and
letting everything be able to inline everything else. No wonder the
first graphical web browser was written for the NeXT :)

Brian

--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
[email protected] [email protected] http://www.[hyperreal,organic].com/