The out of box experience: lessons learned creating compelling VRML 2.0 content
VRML '97 Proceedings of the second symposium on Virtual reality modeling language
VRML in architectural construction documents: a case study
Proceedings of the third symposium on Virtual reality modeling language
Using VRML as an interface to the 3D data warehouse
Proceedings of the third symposium on Virtual reality modeling language
An interactive land use VRML application (ILUVA) with servlet assist
Proceedings of the 32nd conference on Winter simulation
Earth's avatar: the Web augmented virtual earth
ACM SIGGRAPH 2003 Web Graphics
Computer Networking: A Top-Down Approach Featuring the Internet
Computer Networking: A Top-Down Approach Featuring the Internet
Gateway and protocol for modern cyberspace
SIGGRAPH '04 ACM SIGGRAPH 2004 Web graphics
| Hi-index | 0.00 |
The Virtual Reality Modeling Language (VRML) ushered in a new era in computer graphics by providing the first international standard 3D format for the Web (web3D). Unfortunately, some who tried VRML applications found they did not work and naturally blamed the language. However, the problem often lay in the sensitivity to different client software environments of the programming interfaces used to extend VRML. In many cases, VRML applications had to be extended to include things VRML lacked, such as sophisticated user interface and interactivity, database access, multiuser support, security and system integration support. These important aspects of modern systems were added via a programming interface (PI), called the External Authoring Interface (EAI). The problem was that applications based on the EAI would not work reliably due to changes in the client environment by competitive commercial stakeholders, affecting things like the support for a required third party programming language. It is this problem that often lead to unsatisfactory user experiences, not VRML itself.Below the client battlefield radar, three small web3D functions accidentally evolved, in symbiosis with the Web, to provide an alternative integration method built on a simple but solid foundation: the Hypertext Transport Protocol (HTTP). HTTP is the protocol from which the very fabric of the Web was woven. This paper presents methods to integrate web3D application components directly via HTTP. The three web3D functions are used in combination to implement a communication cycle that makes use of persistent state stored in web services. The approach uses open standards, is portable across platforms and resilient to changes in client environment. Applications based on this approach will work more reliably on disparate end user systems and enable developers to leverage increasingly sophisticated web advances.