# Re: x-uri draft

Alexander Dupuy (dupuy@smarts.com)
Mon, 7 Nov 1994 17:45:57 -0500

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Ned Freed: "Re: x-uri draft"
- Previous message: Roy T. Fielding: "Re: How to request internet draft name"
- Maybe in reply to: Martin Hamilton: "x-uri draft"
- Next in thread: Ned Freed: "Re: x-uri draft"

    Date: Mon, 7 Nov 1994 17:45:57 -0500

    From: dupuy@smarts.com (Alexander Dupuy)

    Message-Id: <9411072245.AA26465@just.smarts.com>

    To: martin@mrrl.lut.ac.uk

    Subject: Re: x-uri draft

Martin writes:
> In addition to the headers you mention, it struck me that it would be
> particularly useful to have something along the lines of an
> X-MessageBody-URI: - roughly analagous to the HTTP URI/Location header
>
> Does that sound sensible ?

If you are thinking of providing a URL which can be used to obtain the
contents of the message, you should consider using a MIME content-type
instead. In fact, you should consider the fact that the MIME external-body
content-type is roughly equivalent to a URL, and ask yourself exactly what you
are gaining by using a URL in this case. Once you've thought this through a
bit, you should take your ideas over to the ietf-types mailing list, where you
will be sure to get more feedback on them.

Or was this MessageBody-URI: header just for providing a location for relative
URLs? I'm not sure how useful that is in the context of a mail message,
unless the mail message is itself an HTML document, in which case, a MIME
content-type is probably the best way to go.

I think that there are probably useful ideas here, but it needs to be reviewed
carefully, because of the potential overlap in functionality with other MIME
mechanisms.

@alex

- Next message: Ned Freed: "Re: x-uri draft"
- Previous message: Roy T. Fielding: "Re: How to request internet draft name"
- Maybe in reply to: Martin Hamilton: "x-uri draft"
- Next in thread: Ned Freed: "Re: x-uri draft"