1) Creation of an e-mail parsing service, whereby people getting
started with VRML could e-mail VRML code to an e-mail address
(yes, this could also be done through WWW cgi), whereupon it
would be parsed or whatever, with the result e-mailed back to
the submitter. Input could be limited to files of a small length.
I think this could help encourage the development of VRML,
particularly by people just getting started (read yours truly
or even most of us).
2) compression .wrl's. Looking at the example files at sdsc,
they are really huge. I know in the Webforce demo SGI says
bandwidth won't be a problem, but some of the examples are
much larger than I'd ever think of downloading through WWW.
Looking at the VRML itself, it seems that it would lend itself
well to extensive compression. Compression could cut down on necessary
storage space, cut down transmission time, and even increase the
number of possible hits/time unit at popular sites.
Should we consider some kind .wrl-compression mirroring,
where we could have the standard .wrl available, but maybe
also have a compressed version with a slightly different extension.
Viewers capable of reading the compressed version would first
lookg for the compressed version, downloading it and then uncompressing
it. If the compressed version does not exist, they can just download
the standard .wrl
Any thoughts?
Adrian
------------------------------------------------
Adrian Scott, Ph.D. ([email protected])
Scott Virtual Theme Parks, [email protected]
http://www.rpi.edu/~scotta/systems.html