got it. Thanks for the response. -- Yusuke Yamamoto yus...@mac.com
this email is: [x] bloggable/tweetable [ ] private follow me on : http://twitter.com/yusukeyamamoto subscribe me at : http://samuraism.jp/ On Jan 4, 2011, at 09:26 , Matt Harris wrote: > Hi Yusuke, > > users/lookup supports POST for historical reasons so support hasn't been > removed. friendships/lookup is more recent and it was decided that the > correct HTTP request for this is a GET. > > Hope that helps, > @themattharris > Developer Advocate, Twitter > http://twitter.com/themattharris > > > On Fri, Dec 31, 2010 at 7:52 AM, Yusuke Yamamoto <yus...@mac.com> wrote: > If it's done by design, it's okay. > I just think it's not consistent with users/lookup method which accepts POST > method. > http://dev.twitter.com/doc/get/users/lookup > > -- > Yusuke Yamamoto > yus...@mac.com > > this email is: [x] bloggable/tweetable [ ] private > follow me on : http://twitter.com/yusukeyamamoto > subscribe me at : http://samuraism.jp/ > > On Jan 1, 2011, at 00:45 , Tom van der Woerdt wrote: > > > Since you're actually GETting information and not POSTing information, yes, > > you should use GET. > > > > Tom > > > > > > On 12/31/10 4:35 PM, Yusuke Yamamoto wrote: > >> Hi, > >> > >> /1/friendships/lookup.json returns "This method requires a GET." with POST > >> method as follows: > >> --------- > >> {"request":"\/1\/friendships\/lookup.json?screen_name=barakobama,twit4j2,twit4jprotected","error":"This > >> method requires a GET."} > >> --------- > >> > >> Is it done by design? > >> The method accepts up to 100 screen names and it would be nice to accept > >> POST method as same as /1/users/lookup. > >> > >> Thanks, > > > > -- > > Twitter developer documentation and resources: http://dev.twitter.com/doc > > API updates via Twitter: http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > > http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > > http://groups.google.com/group/twitter-development-talk > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
