@Contract(threading=STATELESS) public class CookiePathComparator extends Object implements Serializable, Comparator<Cookie>
Cookie
header such
that those with more specific Path attributes precede those with
less specific.
This comparator assumes that Path attributes of two cookies path-match a commmon request-URI. Otherwise, the result of the comparison is undefined.
Modifier and Type | Field and Description |
---|---|
static CookiePathComparator |
INSTANCE |
Constructor and Description |
---|
CookiePathComparator() |
Modifier and Type | Method and Description |
---|---|
int |
compare(Cookie c1,
Cookie c2)
Compares its two arguments for order.
|
clone, equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
equals
public static final CookiePathComparator INSTANCE
public int compare(Cookie c1, Cookie c2)
Comparator
In the foregoing description, the notation sgn(expression ) designates the mathematical signum function, which is defined to return one of -1, 0, or 1 according to whether the value of expression is negative, zero or positive.
The implementor must ensure that sgn(compare(x, y)) == -sgn(compare(y, x)) for all x and y. (This implies that compare(x, y) must throw an exception if and only if compare(y, x) throws an exception.)
The implementor must also ensure that the relation is transitive: ((compare(x, y)>0) && (compare(y, z)>0)) implies compare(x, z)>0.
Finally, the implementor must ensure that compare(x, y)==0 implies that sgn(compare(x, z))==sgn(compare(y, z)) for all z.
It is generally the case, but not strictly required that (compare(x, y)==0) == (x.equals(y)). Generally speaking, any comparator that violates this condition should clearly indicate this fact. The recommended language is "Note: this comparator imposes orderings that are inconsistent with equals."
compare
in interface Comparator<Cookie>
c1
- the first object to be compared.c2
- the second object to be compared.