Implementations of this interface is mainly used by ContentDatabase to specify how the differences in file contents will be handled. The common implementations include logic for creating content descriptors based on file attributes (size, modification time) or hashing the file contents (MD5).
Implementations should adhere to the equals(
public boolean | Checks if this supplier will calculate the same content descriptors as the parameter given the same
circumstances. |
public ContentDescriptor | get( Creates the content descriptor for the given location. |
public default ContentDescriptor | getCalculatedOutput( Computes the content descriptor based on the data calculated. |
public default ByteSink | Creates a content descriptor calculating output. |
public default ContentDescriptor | getUsingFileAttributes( Creates the content descriptor for a file, optionally using the provided attributes. |
public default ContentDescriptor | getUsingFileContent( Creates the content descriptor for a file, optionally using the provided contents or attributes. |
public int | hashCode() Returns a hash code value for the object. |
Indicates whether some other object is "equal to" this one.
The equals
method implements an equivalence relation on non-null object references:
- It is reflexive: for any non-null reference value
x
,x.equals(x)
should returntrue
. - It is symmetric: for any non-null reference values
x
andy
,x.equals(y)
should returntrue
if and only ify.equals(x)
returnstrue
. - It is transitive: for any non-null reference values
x
,y
, andz
, ifx.equals(y)
returnstrue
andy.equals(z)
returnstrue
, thenx.equals(z)
should returntrue
. - It is consistent: for any non-null reference values
x
andy
, multiple invocations ofx.equals(y)
consistently returntrue
or consistently returnfalse
, provided no information used inequals
comparisons on the objects is modified. - For any non-null reference value
x
,x.equals(null)
should returnfalse
.
The equals
method for class Object
implements the most discriminating possible equivalence
relation on objects; that is, for any non-null reference values x
and y
, this method returns
true
if and only if x
and y
refer to the same object (x == y
has the value
true
).
Note that it is generally necessary to override the hashCode
method whenever this method is overridden,
so as to maintain the general contract for the hashCode
method, which states that equal objects must have
equal hash codes.
true
if this object is the same as the obj argument; false
otherwise.
Implementations can return a custom output stream which will receive the contents of the file. The
getCalculatedOutput(
This functionality is optional, not required to be supported by implementations.
Implementing this function for content hash based implementations can improve performance.
null
if this functionality is not supported.null
if it is not available (null
attributes doesn't
mean that the file doesn't exist).
The general contract of hashCode
is:
- Whenever it is invoked on the same object more than once during an execution of a Java application, the
hashCode
method must consistently return the same integer, provided no information used inequals
comparisons on the object is modified. This integer need not remain consistent from one execution of an application to another execution of the same application. - If two objects are equal according to the
equals(Object)
method, then calling thehashCode
method on each of the two objects must produce the same integer result. - It is not required that if two objects are unequal according to the
Object.equals(
Object) method, then calling thehashCode
method on each of the two objects must produce distinct integer results. However, the programmer should be aware that producing distinct integer results for unequal objects may improve the performance of hash tables.
As much as is reasonably practical, the hashCode method defined by class Object
does return distinct
integers for distinct objects. (This is typically implemented by converting the internal address of the object
into an integer, but this implementation technique is not required by the Java™ programming language.)