[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What is CONTENT?
- To: <firstname.lastname@example.org>
- Subject: Re: What is CONTENT?
- From: "Hilarie Orman" <HORMAN@novell.com>
- Date: Fri, 10 Nov 2000 11:24:09 -0700
- Delivery-date: Fri, 10 Nov 2000 10:25:06 -0800
- Envelope-to: email@example.com
It's just an encoding of application-level data, isn't it?
Of course it's digital, this is the Internet; it's most probably octets, but
that's not a particularly helpful part of the definition; same for "ordered".
The type can be specified in the encoding; that's normal.
This verges on a rat hole, methinks.
>>> Alex French <firstname.lastname@example.org> 11/10/00 06:18AM >>>
There could also be more meta-data, e.g. a content-length header. How about
"An ordered sequence of octets, plus associated metadata". I'd keep away
from "finite" since a live stream must be treated as potentially infinite
(ie, you don't want to try and store the whole thing before forwarding).
At 04:57 PM 08/11/2000, Barron Housel wrote:
>By "typed" I simply meant the type of the content via the "content-type" http
>header: txt/html, jpeg, gif, mpeg, etc. The type is necessary to tell the CDN
>surrogate how to deliver the data stream -- e.g., real time streaming
>audio/video or file transfer.
>Alex French wrote:
> > At 11:09 PM 07/11/2000, Mark Day wrote:
> > >Barron's suggestion is that CONTENT is a "typed finite sequence of
> > >While this is correct, it seems incomplete.
> > I'm unclear as to what "typed" means in this context.
> > --
> > Alex French
> > Consultant, Technical Services E: email@example.com
> > VIA NET.WORKS, Inc. T: +353 86 818 8118
Consultant, Technical Services E: firstname.lastname@example.org
VIA NET.WORKS, Inc. T: +353 86 818 8118