class
MultiPartBody extends BodyPart
Instance Constructors
-
new
MultiPartBody(parts: Map[String, BodyPart], subtype: String = "form-data")(implicit scheduler: Scheduler)
Value Members
-
final
def
!=(arg0: AnyRef): Boolean
-
final
def
!=(arg0: Any): Boolean
-
final
def
##(): Int
-
final
def
==(arg0: AnyRef): Boolean
-
final
def
==(arg0: Any): Boolean
-
final
def
asInstanceOf[T0]: T0
-
val
boundary: String
-
def
clone(): AnyRef
-
def
content: Observable[ByteBuffer]
-
def
contentType: String
-
final
def
eq(arg0: AnyRef): Boolean
-
def
equals(arg0: Any): Boolean
-
def
finalize(): Unit
-
final
def
getClass(): Class[_]
-
def
hashCode(): Int
-
final
def
isInstanceOf[T0]: Boolean
-
final
def
ne(arg0: AnyRef): Boolean
-
final
def
notify(): Unit
-
final
def
notifyAll(): Unit
-
final
def
synchronized[T0](arg0: ⇒ T0): T0
-
def
toString(): String
-
final
def
wait(): Unit
-
final
def
wait(arg0: Long, arg1: Int): Unit
-
final
def
wait(arg0: Long): Unit
Inherited from AnyRef
Inherited from Any
A body made of multiple parts.
Usage: A multipart body acts as a container for other bodies. For instance, the multipart body is commonly used to send a form with binary attachments in conjunction with the ByteBufferBody. For simple key/value pairs, use URLEncodedBody instead.
Safety consideration: A random boundary is generated to separate parts. If the boundary was to occur within a body part, it would mess up the whole body. In practice, the odds are extremely small though.