Companion¶

[jvm]\ object Companion

Properties¶

Name	Summary
ALTERNATIVE	[jvm] @JvmField val ALTERNATIVE: MediaType The "multipart/alternative" type is syntactically identical to "multipart/mixed", but the semantics are different. In particular, each of the body parts is an "alternative" version of the same information.
DIGEST	[jvm] @JvmField val DIGEST: MediaType This type is syntactically identical to "multipart/mixed", but the semantics are different. In particular, in a digest, the default `Content-Type` value for a body part is changed from "text/plain" to "message/rfc822".
FORM	[jvm] @JvmField val FORM: MediaType The media-type multipart/form-data follows the rules of all multipart MIME data streams as outlined in RFC 2046. In forms, there are a series of fields to be supplied by the user who fills out the form. Each field has a name. Within a given form, the names are unique.
MIXED	[jvm] @JvmField val MIXED: MediaType The "mixed" subtype of "multipart" is intended for use when the body parts are independent and need to be bundled in a particular order. Any "multipart" subtypes that an implementation does not recognize must be treated as being of subtype "mixed".
PARALLEL	[jvm] @JvmField val PARALLEL: MediaType This type is syntactically identical to "multipart/mixed", but the semantics are different. In particular, in a parallel entity, the order of body parts is not significant.