W3C home > Mailing lists > Public > xml-dist-app@w3.org > December 2000

RE: [DR008] - passing arbitrary content

From: Dick Brooks <dick@8760.com>
Date: Tue, 5 Dec 2000 21:26:12 -0600
To: "Mike Dierken" <mike@DataChannel.com>, <xml-dist-app@w3.org>
Message-ID: <NDBBIOBLMLCDOHCHIKMGIEACEKAA.dick@8760.com>
RE: [DR008] - passing arbitrary contentMike D wrote:
>Using MIME multipart/related allows for the URI to reference another
portion of the message that was delivered. This only requires that
boundaries between addressable

>portions be clearly marked within a message - HTTP and SMTP both have that
when they use MIME multipart syntax.

I agree. In this case Content-ID's could provide a unique reference
identifier in the URI.


Dick Brooks
Group 8760
110 12th Street North
Birmingham, AL 35203
dick@8760.com
205-250-8053
Fax: 205-250-8057
http://www.8760.com/

InsideAgent - Empowering e-commerce solutions

  -----Original Message-----
  From: xml-dist-app-request@w3.org [mailto:xml-dist-app-request@w3.org]On
Behalf Of Mike Dierken
  Sent: Tuesday, December 05, 2000 5:51 PM
  To: 'xml-dist-app@w3.org'
  Subject: RE: [DR008] - passing arbitrary content


  >
  > Accessing binary data thru a URI (pass be reference semantics) requires
  > binary data to be accessible
  > from the Internet (in e-commerce scenarios), for example on a web (or
FTP)
  > server.

  Using MIME multipart/related allows for the URI to reference another
portion of the message that was delivered. This only requires that
boundaries between addressable portions be clearly marked within a message -
HTTP and SMTP both have that when they use MIME multipart syntax.

  Mike D
Received on Tuesday, 5 December 2000 22:30:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:57 GMT