Lists Home |
Date Index |
- From: "Jonathan Borden" <firstname.lastname@example.org>
- To: "xml" <email@example.com>, <firstname.lastname@example.org>
- Date: Tue, 20 Apr 1999 21:33:31 -0400
> Using mime attachments and such is so inefficient... would they really
> opt for storing binary object attributes using text-encoding approaches?
MIME parts can be and often are binary. For example when you view a GIF or
JPEG image on the Web (i.e. using HTTP), they are transmitted quite
efficiently as a MIME message of Content-Type: image/jpeg and
Content-transfer-encoding: binary. It is SMTP protocol that results in
transmission with a Content-transfer-encoding: base64 though ESMTP can
handle binary data as well.
> ...I'm used to seeing binary and text mix and
> if the binary was inside of a (predictable) XML tag that would be
> just dandy!
Dandy, but something else than XML... this can be your own private data
format. Oh darn that inconvenient spec :-)
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)