It seems reasonable that the compression utility could be embedded into the
VRML file creator; in a similar manner, the decompression utility could be
embedded into the VRML file parser. Given this - there's no clear reason to
use GZIP, is there? - there should be no process overhead associated with
sending smaller files versus sending larger files.
There has been some question as to the relevance of this entire thread;
download time is very important for the universe of VRML users who will be
purusing our sites in the next 6 - 12 months. Saving 30 - 50% over and
above normal compression techniques by using a comprehensive
tokenizaion/numeric representation/compression scheme is therefore a
worthwhile goal.
I have almost always used Internet over a 14.4 Kbps dialup SLIP (TIA) line -
as I am now. It has made me acutely conscious of file download times, and
has thoroughly convinced me that we really do need to attack this problem in
a substantial manner.
Mark