scott at tranzoa.com
Wed Aug 11 09:44:08 CDT 1999
This was a thing I was quite confused about. You'll notice in addition
Content Headers, I said that you could put them on in, but that we probably
would't bring them through. Should I not? It kinda breaks the standard...
* Patrick McCuller translated into ASCII [Wed, Aug 11, 1999 at 05:08:04AM -0400][<01df01bee3d9$050562c0$1b76c897 at scylla>]
> This is a great document. Thanks, Scott.
> I've bumped into Content-Language (RFC1766)(which will make some people on
> this list very happy) and Content-Disposition, as well as Content-MD5
I can't find RFC 1766 nor info on Content-Disposition. Could you e-mail a
link? I can guess Content-MD5 is just a MD5 of the contained data, right?
> I have a general question about integrating this sort of thing. I guess
> we're likely to see any number of Content-X-Blah MIME headers? In that case,
> should our approach be to simply add attribute after attribute to the <mime>
> element, or should we take a different course? Jer?
That approach works as long as we specify for whoever forwards a <mime> tag
to preserve all tags.
> > -----Original Message-----
> > From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
> > Scott Robinson
> > Sent: Wednesday, August 11, 1999 4:40 AM
> > To: jdev at jabber.org
> > Subject: [JDEV] MIME
> > Fine then. Let me up the ante.
> > http://dsn.itgo.com/MIME.html
> > Scott.
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> jdev mailing list
> jdev at jabber.org
More information about the JDev