Re: Common Objects
Brian Behlendorf ([email protected])
Wed, 31 May 1995 20:02:29 -0700 (PDT)
On Tue, 30 May 1995, Mark Waks wrote:
> Mitra writes:
> >I believe that the
> >world builder is the one who should control what gets seen, so as an object
> >builder I put together a kitchen and say that I'd like this really cool
> >teapot, but in its abscence I'm willing to put up with the generic teapot
> >that is specified here, I'm typicalyl not going to want to allow just any
> >old thing that someone else has called a teapot
>
> Yes, but *I* am. The point here is not to force generics on those who
> want specifics -- it's simply to come up with a generics mechanism for
> those of us who do *not* care. There's an element of caveat emptor here;
> yes, there will be pathological cases where a thingy that's been loaded
> just makes no sense in context. I suspect they won't be overly common,
> though, and I'm willing to put up with a little occasional chaos in the
> name of making things generally run faster. You don't have to...
There's still the situation where I inline someone else's teapot into my
scene and they go and change it to a bust of Beethoven, either through
maliciousness or ineptitude or just plain sillyness. That would happen today
if more people did used IMG SRC on off-site objects. Check some of the
"Piazza People" thread posts on hotwired to see what happens when this is
overused :) HTML 3.0 has a proposed "MD5" attribute (I think that's what it's
called) on all tags that reference external objects - the idea being that at
document creation time I can do a checksum of an object I'm inlining and
put that checksum at the value of the MD5 tag, so people seeing my scene
can at least know that the teapot masquerading as a bust of Beethoven was
different than the object I the inliner thought I was inlining.
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
[email protected] [email protected] http://www.[hyperreal,organic].com/