Package org.jboss.resteasy.reactive.client.impl.multipart

Class QuarkusMultipartFormUpload

java.lang.Object

org.jboss.resteasy.reactive.client.impl.multipart.QuarkusMultipartFormUpload

All Implemented Interfaces:

io.vertx.core.streams.ReadStream<io.vertx.core.buffer.Buffer>, io.vertx.core.streams.StreamBase, Runnable

public class QuarkusMultipartFormUpload
extends Object
implements io.vertx.core.streams.ReadStream<io.vertx.core.buffer.Buffer>, Runnable

based on MultipartFormUpload

Constructor Summary

Constructors

Constructor	Description
QuarkusMultipartFormUpload(io.vertx.core.Context context, QuarkusMultipartForm parts, boolean multipart, PausableHttpPostRequestEncoder.EncoderMode encoderMode)

Method Summary

Modifier and Type	Method	Description
QuarkusMultipartFormUpload	endHandler(io.vertx.core.Handler<Void> handler)
QuarkusMultipartFormUpload	exceptionHandler(io.vertx.core.Handler<Throwable> handler)
io.vertx.core.streams.ReadStream<io.vertx.core.buffer.Buffer>	fetch(long amount)
QuarkusMultipartFormUpload	handler(io.vertx.core.Handler<io.vertx.core.buffer.Buffer> handler)
io.vertx.core.MultiMap	headers()
QuarkusMultipartFormUpload	pause()
io.vertx.core.streams.Pipe<io.vertx.core.buffer.Buffer>	pipe()	The reason we need a custom Pipe here is that if we don't manually throttle the read stream, the fact that the underlying connection is shared can lead to exhaustion of heap memory.
QuarkusMultipartFormUpload	resume()	Deprecated.
void	run()

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface io.vertx.core.streams.ReadStream

pipeTo, pipeTo

Constructor Detail

QuarkusMultipartFormUpload

public QuarkusMultipartFormUpload(io.vertx.core.Context context,
                                  QuarkusMultipartForm parts,
                                  boolean multipart,
                                  PausableHttpPostRequestEncoder.EncoderMode encoderMode)
                           throws Exception

Throws:

Exception

Method Detail

run

public void run()

Specified by:

run in interface Runnable

headers

public io.vertx.core.MultiMap headers()

exceptionHandler

public QuarkusMultipartFormUpload exceptionHandler(io.vertx.core.Handler<Throwable> handler)

Specified by:

exceptionHandler in interface io.vertx.core.streams.ReadStream<io.vertx.core.buffer.Buffer>

Specified by:

exceptionHandler in interface io.vertx.core.streams.StreamBase

handler

public QuarkusMultipartFormUpload handler(io.vertx.core.Handler<io.vertx.core.buffer.Buffer> handler)

Specified by:

handler in interface io.vertx.core.streams.ReadStream<io.vertx.core.buffer.Buffer>

pause

public QuarkusMultipartFormUpload pause()

Specified by:

pause in interface io.vertx.core.streams.ReadStream<io.vertx.core.buffer.Buffer>

fetch

public io.vertx.core.streams.ReadStream<io.vertx.core.buffer.Buffer> fetch(long amount)

Specified by:

fetch in interface io.vertx.core.streams.ReadStream<io.vertx.core.buffer.Buffer>

resume

@Deprecated
public QuarkusMultipartFormUpload resume()

Deprecated.

Specified by:

resume in interface io.vertx.core.streams.ReadStream<io.vertx.core.buffer.Buffer>

endHandler

public QuarkusMultipartFormUpload endHandler(io.vertx.core.Handler<Void> handler)

Specified by:

endHandler in interface io.vertx.core.streams.ReadStream<io.vertx.core.buffer.Buffer>

pipe

public io.vertx.core.streams.Pipe<io.vertx.core.buffer.Buffer> pipe()

The reason we need a custom Pipe here is that if we don't manually throttle the read stream, the fact that the underlying connection is shared can lead to exhaustion of heap memory. See this for more details.

Specified by:

pipe in interface io.vertx.core.streams.ReadStream<io.vertx.core.buffer.Buffer>