Restful URLs with data in query string or request body?
What's the rule of thumb for passing data in a REST URL in the query string vs. the body of a request?
Ie: You're creating a service to add hockey players. You could go with:
PUT /players
{ "name": Gretzky }
or
PUT /players?name=Gretzky
If you're passing a lot of data, you would need to go with option #1 as there is a limit on the URL length. But other than this, why not just use the query string to pass data?
Update: Removed comment that you could test option #2 in a browser. Realized (duh) that you can only do GET-s in your browser.
Answer
Based on HTTP's definition of PUT, your first request is overwriting the list of players with a new list that contains just one player name. It is not adding to the list of players.
The second option does not really make much sense to me. Doing PUT without a body is not really consistent with the meaning of PUT.
Considering that one of the standard definitions of POST is to append to an existing resource, I'm not sure why you wouldn't do
POST /players
{ "name": Gretzky }
If you are sure that all you player names are going to be unique then you could use PUT like this:
PUT /player/Gretzky
{ "name": Gretzky }
When you decide to do REST on HTTP you are agreeing to use HTTP in the way that is defined in RFC2616. That's what the uniform interface constraint means. And just to be pedantic, there is no such thing as a REST URL and you can't test either option in a browser because without javascript, you can't do a PUT in a browser.