All Downloads are FREE. Search and download functionalities are using the official Maven repository.

io.gravitee.gateway.jupiter.api.context.HttpResponse Maven / Gradle / Ivy

/**
 * Copyright (C) 2015 The Gravitee team (http://gravitee.io)
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *         http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package io.gravitee.gateway.jupiter.api.context;

import io.gravitee.gateway.api.buffer.Buffer;
import io.reactivex.rxjava3.core.Completable;
import io.reactivex.rxjava3.core.Flowable;
import io.reactivex.rxjava3.core.FlowableTransformer;
import io.reactivex.rxjava3.core.Maybe;
import io.reactivex.rxjava3.core.MaybeTransformer;
import io.reactivex.rxjava3.core.Single;

public interface HttpResponse extends GenericResponse {
    /**
     * Get the current body response as a {@link Maybe}. If no body has not been set on the response yet, an empty {@link Maybe} will returned.
     *
     * By getting the body as a {@link Maybe}, the current body chunks will be merged together to reconstruct the entire body in provide it in the form of a single {@link Buffer}
     * This is useful when the entire body is required to apply some transformation or any manipulation.
     *
     * WARN: beware that the entire body content will be loaded in memory. You should not keep a direct reference on the body chunks as they could be overridden by others at anytime.
     *
     * @return a {@link Maybe} observable containing the current entire body response or empty if response body as not been set yet.
     * @see #bodyOrEmpty()
     */
    Maybe body();

    /**
     * Same as {@link #body()} but returns a {@link Single} of {@link Buffer} instead.
     *
     * If no body response as been set yet, it returns a {@link Single} with an empty {@link Buffer}.
     * It is a convenient way that avoid checking if the body is set or not prior to manipulate it.
     *
     * @return a {@link Single} observable containing the current entire body response or empty an {@link Buffer) if response body as not been set yet.
     * @see #body()
     */
    Single bodyOrEmpty();

    /**
     * Set the current body response as a {@link Buffer}.
     * This is useful when you want to replace the current body response with a specific content that doesn't come from a reactive chain, ex:
     *
     * 
     *     response.body(Buffer.buffer("My custom content");
     * 
     *
     * WARN:
     * 
    *
  • replacing the request body will NOT "drain" the previous request that was in place.
  • *
  • You MUST ensure to consume the previous body by yourself when using it.
  • *
  • You SHOULD consider using {@link #onBody(MaybeTransformer)} to change the body during the chain execution.
  • *
* * @see #onBody(MaybeTransformer) * @see #chunks(Flowable) */ void body(final Buffer buffer); /** * Applies a transformation on the complete body given as a single {@link Buffer}. * * Ex: * * response.onBody(body -> body.map(buffer ->Buffer.buffer(buffer.toString().toUpperCase()))); * * * IMPORTANT: applying a transformation on the body content loads the whole body in memory. * It's up to the consumer to make sure it is safe to do that without consuming too much memory. * * @param onBody the transformation that will be applied on the body. * @return a {@link Completable} that completes once the body transformation has occurred. */ Completable onBody(final MaybeTransformer onBody); /** * Set the current response body chunks from a {@link Flowable} of {@link Buffer}. * This is useful to directly pump the upstream chunks to the downstream without having to load all the chunks in memory. * * WARN: *
    *
  • replacing the response chunks will NOT "drain" the previous response that was in place.
  • *
  • You MUST ensure to consume the previous chunks by yourself when using it.
  • *
  • You SHOULD consider using {@link #onChunks(FlowableTransformer)} to change the chunks during the chain execution.
  • *
* * @param chunks the {@link Flowable} of chunks representing the response to push back to the downstream. * * @see #body() */ void chunks(final Flowable chunks); /** * Get the current response body chunks as {@link Flowable} of {@link Buffer}. * This is useful when you want to manipulate the entire body without having to load it in memory. * * WARN: you should not keep a direct reference on the body chunks as they could be overridden by others at anytime. * * @return a {@link Flowable} containing the current body response chunks. */ Flowable chunks(); /** * Applies a transformation on each body chunks and completes when all the chunks have been processed. * Ex: * * response.onChunks(chunks -> chunks.map(buffer -> Buffer.buffer(buffer.toString().toUpperCase()))); * * * IMPORTANT: applying a transformation on the body chunks loads the whole body in memory. * It's up to the consumer to make sure it is safe to do that without consuming too much memory. * * IMPORTANT: applying a transformation on chunks completes when all chunks have been transformed. * If used in a policy chain, it means that the next policy will start once all chunks have been transformed * * @param onChunks the transformer that will be applied. * @return a {@link Completable} that completes once the body transformation has occurred on all the chunks. */ Completable onChunks(final FlowableTransformer onChunks); /** * End the response. * * @return an observable that can be easily chained. */ Completable end(); }




© 2015 - 2025 Weber Informatics LLC | Privacy Policy