W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2004

Re: Propsed new issue: variability of encoding in Miffy

From: Amelia A Lewis <alewis@tibco.com>
Date: Thu, 15 Jan 2004 10:47:51 -0500
To: Anish Karmarkar <Anish.Karmarkar@oracle.com>
Cc: xml-dist-app@w3.org
Message-id: <20040115104751.57e74bef.alewis@tibco.com>

On Wed, 14 Jan 2004 09:13:45 -0800
Anish Karmarkar <Anish.Karmarkar@oracle.com> wrote:
> Is this stated in RFC 2045? Or does this occur in some other spec?
> I could not locate this in RFC 2045. But I could have missed it.

See RFC 2049 (MIME Conformance), section 3, especially item 6.  2049 is
probably well worth reading for the MTOM/MIFFY authors: it not only
discusses how broken implementations should be handled, it effectively
provides the motivation for why things are as they are in MIME.  And
outlines, clearly, what it means to be MIME conformant.  Being MIME
conformant isn't an issue for this group, I think, but it is probably
worthwhile to keep the design constraints (and messy real-world
implementation pressures) in mind.

In summary, 2049 says that changing the content of a message is BAD and
BROKEN.  And that it happens anyway, in ways that are relatively easy to
handle, so be prepared.

Amy!
-- 
Amelia A. Lewis
Architect, TIBCO/Extensibility, Inc.
alewis@tibco.com
Received on Thursday, 15 January 2004 11:04:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 22:28:13 UTC