scott at tranzoa.com
Wed Aug 11 11:09:35 CDT 1999
Since the three of us seem to agree on adding headers straight to the
<mime/> tag, I'll change that section of the spec.
* Jeremie translated into ASCII [Wed, Aug 11, 1999 at 11:04:43AM -0500][<Pine.LNX.4.10.9908111059260.26114-100000 at lor.jeremie.com>]
> > 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
> > headers.
> Sounds good, more options and flexibility for the clients that require it
> is always a good thing, as long as they are explained clearly and things
> don't get too confusing :)
> > 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?
> I think adding them to <mime/> is fine for the time being... if it becomes
> a problem or is used excessively, it's probably a feature that should be
> looked at for inclusion in some other fashion anyway.
> jdev mailing list
> jdev at jabber.org
More information about the JDev