>The *only* thing that VRML and WWW share is the use of URLs.
This statement is incorrect.
Without sounding to repetitive, let me state again: VRML is a *networking*
technology. VRML happens to share libwww, which is HTTP, FTP, etc.
(otherwise WWWInline wouldn't work), and will most likely use features
garnered from HTTP-NG, RTP, MBONE, JAVA, and other technologies. These are
network technologies. As few of you have perhaps implemented VRML browsers,
let me share some of my experience with you: Very very little of the work
is in the graphics and rendering- much much much of the work is in the
networking.
As far as I know, VRML has very little more progress to make on the
"graphics" front. Sound is not a graphics issue, nor is caching nor, even,
is interactivity. The first and last of these are clearly more
network-based issues/implementations than graphics technologies.
My recommendation stands: comp.infosystems.www.vrml
Mark
________________________________________
Mark D. Pesce
General Partner,
The Community Company * 415.621.1981 * [email protected]