RESTful API Request
0 views
Skip to first unread message
SP
May 5, 2007, 4:29:52 PM5/5/07
to Twitter Development Talk
I did wish to make a request to fix the API to actually be RESTful.
Currently the following request yields a 200/OK HTTP response, when
RESTful conventions dictate it should yield a 201/Created HTTP
response for successful cases:
Currently the following request yields a 200/OK HTTP response, when
RESTful conventions dictate it should yield a 201/Created HTTP
response for successful cases:
POST /update
status=url+escaped+status
Can you comment on why this was done?
Thanks,
Susan
SP
May 5, 2007, 5:26:19 PM5/5/07
to Twitter Development Talk
Correction: should have said:
> POST /statuses/update
> status=url+escaped+status
> POST /statuses/update
> status=url+escaped+status
If you would like to view a status as simply mutable, then you should
probably be using a singleton/singular resource and using the PUT HTTP
method to updates, since this is technically more correct.
Just a few suggestions since the API Documentation does state the API
is "RESTful". Perhaps you can actually make the API truly conform to
RESTful conventions soon?
Reply all
Reply to author
Forward
0 new messages