404 is your best response. According to the HTTP RFC, http://www.ietf.org/rfc/rfc2616.txt, A 400 Bad Request means: The request could not be understood by the server due to malformed syntax. Whereas, 404 states: The server has not found anything matching the Request-URI. The entire URI is your resource identifier, and you’re not finding a matching resource … Read more
Of the three I prefer the third option, it’s not uncommon to see that syntax; e.g. parts of Twitter’s API allow that syntax: https://dev.twitter.com/rest/reference/get/statuses/show/id A fourth option is a hybrid approach, where you pick one (say, ID) as the typical access method for single items, but also allow queries based on the slug. E.g.: GET … Read more
Boolean is an immutable value object. It was designed to be unchanging and made final in order to enforce that. java.lang.Boolean has been around since 1.0. AtomicBoolean is mutable, and designed to get updated so that the updated value is visible across threads. AtomicBoolean was introduced with Java 5. These are entirely different concepts, which … Read more
I don’t see how REST adds a constraint that two resources could not have the same value. The resourceType/ID is just an example of the easiest use case rather than the best way to go from a RESTful point of view. If you read paragraph 5.2.1.1 of Roy Fielding’s dissertation carefully, you will notice that … Read more
There’s no standard for it. Just have a look around: there are hundreds of thousands of APIs using different approaches. Most of APIs I know use one of the following approaches for pagination: offset and limit or page and size Both can be 0 or 1 indexed. Which is better? That’s up to you. Just … Read more
Anything but return this == other would be counter intuitive and violate the principle of least astonishment. Two enum constants are expected to be equal if and only if they are the same object and the ability to override this behavior would be error prone. Same reasoning applies to hashCode(), clone(), compareTo(Object), name(), ordinal(), and … Read more
.load() is overloaded with entirely different behavior depending on the arguments passed .toggle() is overloaded with entirely different behavior depending on the arguments passed too much overloading of the jQuery() function perhaps. the .attr() you mentioned. The distinction from properties should have been immediate IMO. .map( key,val ) but $.map( val,key ), and the this … Read more
From Best Practices for Exception Handling: Try not to create new custom exceptions if they do not have useful information for client code. What is wrong with the following code? public class DuplicateUsernameException extends Exception {} It is not giving any useful information to the client code, other than an indicative exception name. Do not … Read more
I think the point is that there is no reason for a getFirst(iterable) in that this could be done with iterable.iterator().next(). Guava makes an excellent attempt to keep the API small and so does not add things that could / should be done easily another way. On the other hand, there is not already a … Read more
In the semi large projects where I usually work (more than 2 million lines of code) I would ban private class functions if I could. The reason being that a private class function is private but yet it’s visible in the header file. This means if I change the signature (or the comment) in anyway … Read more