org.dmfs.httpessentials.methods

Class IdempotentMethod

java.lang.Object

org.dmfs.httpessentials.methods.AbstractMethod

org.dmfs.httpessentials.methods.IdempotentMethod

All Implemented Interfaces:

HttpMethod

public final class IdempotentMethod
extends AbstractMethod

An idempotent HttpMethod that's not safe. For idempotent Methods that are also safe use SafeMethod.

See Also:

RFC 7231, section 4.2.1, RFC 7231, section 4.2.2

Field Summary

Fields inherited from interface org.dmfs.httpessentials.HttpMethod

CONNECT, DELETE, GET, HEAD, OPTIONS, PATCH, POST, PUT, TRACE

Constructor Summary

Constructors

Constructor and Description
IdempotentMethod(java.lang.String verb, boolean supportsRequestPayload)

Method Summary

Modifier and Type	Method and Description
boolean	isIdempotent() Returns if this request method is idempotent, which means that sending multiple identical requests with that method has the same effect as sending one single request to the server.
boolean	isSafe() Returns if this request method is safe, which means that the request is not intended and not expected to change any state on the server.

Methods inherited from class org.dmfs.httpessentials.methods.AbstractMethod

equals, hashCode, supportsRequestPayload, verb

Methods inherited from class java.lang.Object

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

Constructor Detail

IdempotentMethod

public IdempotentMethod(java.lang.String verb,
                        boolean supportsRequestPayload)

Method Detail

isSafe

public boolean isSafe()

Description copied from interface: HttpMethod

Returns if this request method is safe, which means that the request is not intended and not expected to change any state on the server. In effect the semantics are to be considered read-only.

See Also:

RFC 7231, Section 4.2.1

isIdempotent

public boolean isIdempotent()

Description copied from interface: HttpMethod

Returns if this request method is idempotent, which means that sending multiple identical requests with that method has the same effect as sending one single request to the server.

See Also:

RFC 7231, Section 4.2.2