[cache]|[gzip]|[holy war]FCC: ~/Mail/out
Matthew Elvey ([email protected])
Tue, 23 May 1995 18:53:50 -0400
>I will point out again that this is why we need a mechanism for
>distributing and/or caching common items -- spaces are a *lot* faster
>to download if you've already got some of the building blocks locally.
>We still haven't addressed this point in any sort of coherent way, and
>really ought to by, at the latest, the time of rollout for 2.0...
The basic implementation of this, as mentioned long ago, is being dealt
with. Browsers already often cache. And there are large
site-level cache systems as well. However, what we really want is a
system that allows a .wrl to specify a fridge in a corner, but have that
fridge description not be d/l'ed from the source, but instead come from
a local description of a generic fridge, which is likely to exist if
we've recently been in a kitchen for example. (As discussed long ago.)
IV is sort of heirarchical (AKA OO) but not really, cuz you just get one
.wrl, as I understand things.
NATHAN J. STRANGE: Not to discourage you, but gzip is very hard to beat.
Anyone who eats their eggs small end first will be shot on sight.
(apropos the home.wrl and Z/X is up holy wars)
--
Matthew Elvey New Haven, CT | My opinions represent the
[email protected] or | official policy of Yale U.,
[email protected] or | all men and the American
(203)772-4826 | Bar Association...NOT!