We're going for more consistency, but also more RESTfulness. So rather than a bunch of "create"s in the method names, you'll POST to a collection you want to add to, and DELETE when you want to remove from it (but since many HTTP libraries don't really support DELETE, we'll provide an alias for that in the URLs).
On Wed, Jan 14, 2009 at 06:36, Abraham Williams <[email protected]> wrote: > I was thinking that it would be good to have more consistency in method > names. This would be best implemented in the next version of the API and > some of it may already be planned. > Currently update, new, create, and follow are all used for creating > something new. Could be simplified to just use create. So it would be: > Create status. > Create direct message. > Create friendship. > Create favorite. > Create notification rule. > Destroy is used for almost everything so only the notifications would have > to be changed to destroy notifications rule. > This would make the API easier to work with as it would have more consistent > terminology. Anytime you want something new use *create* any time you want > to get rid of something use *destroy*. Thoughts? > -- > | Abraham Williams | http://the.hackerconundrum.com > | Web608 | Community Evangelist | http://web608.org > | gg&d | betaGeek | http://girlsgeeksanddating.com > | Micro-email: http://userscripts.org/scripts/show/38822 > | This email is: [] blogable [x] ask first [] private > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
