[Top] [All Lists]

Re: Content-Disposition Header

1993-06-28 13:00:16
To:  Keith Moore <moore(_at_)cs(_dot_)utk(_dot_)edu>
Subject:  Re: Content-Disposition Header
Date:  Sat, 26 Jun 1993 18:34:02 -0400 (EDT)

Excerpts from mail: 26-Jun-93 Re: Content-Disposition Hea.. Keith
Moore(_at_)cs(_dot_)utk(_dot_)edu (1242)

This works as long as "hidden" body parts are required to preceed
the parts that reference them.

Which we could require, if we're willing to state that there's never any
circularities.  Can an object have both "owner" & "requires"?  Can these
things nest or be mutually referential?  How hard it will be to
implement depends on this.  A general-purpose implementation has to be
fairly complex, but if we're willing to say that there's no cycles
(possibly because you can't have both owner  & requires, or possibly
just because you aren't allowed to have cycles, so cycles can be treated
as errors) then a linear implementation is more plausible, but the
general mechanism is less powerful.

I just realized that I might want to mail someone a set of application/html
docs that have cyclic references among one another.  Hmmm...