There are a number of JSON implementations in languages like Javascript and
ActionScript that result in truncation of larger integers. Recently
Twitter's id-generation scheme for Tweets changed, resulting in larger
integers. id_str is provided so that you have a string-based representation
of nearly any identifier in Twitter's API, the only safe way to consume the
identifier in languages with this problem.
In most cases, it's safest/best to use id_str when it's provided.
Taylor
On Mon, Dec 20, 2010 at 2:17 AM, Rajesh <ssrajesh....@gmail.com> wrote:
> please help me how to get id_str
>
> what is id_str?
>
> public function statusUpdates($token,$message)
> {
> global $logger;
> $client = $token->getHttpClient($this->option_array);
> $message_encode=$message;
> $client->setUri('
> http://api.twitter.com/1/statuses/update.json');
> $client->setParameterPost('status',$message_encode);
> $client->setMethod(Zend_Http_Client::POST);
> $response = $client->request('POST');
> //$content = $response->getBody();
> }
>
> /*
> * TO SEND JOB DETAILS MESSAGE TO Twitter CONNECTIONS
> */
> public function sendMessage($token, $sender_id=null, $message)
> {
> global $logger;
> $client = $token->getHttpClient($this->option_array);
> $sender_id = explode(',',$sender_id);
> $message_encode=urlencode($message);
>
> // Set Method (GET, POST or PUT)
> $client->setUri('
> http://api.twitter.com/1/statuses/update.json');
> for($i=0;$i<count($sender_id);$i++)
> {
> $message_text = 'd '.$sender_id[$i].' '.$message;
>
> $client->setParameterPost('message',$message_encode);
> $client->setParameterPost('status',$message_text);
> $client->setMethod(Zend_Http_Client::POST);
> $response =$client->request('POST');
> //$content = $response->getBody();
> //$response_content = $response->getHeader();
> }
> }
> /**
> * Assues there is already a valid token available for this user
> */
> public function getConnections($token)
> {
> global $logger;
> $twitter_con_arr = array();
> if ($token == null)
> return $twitter_con_arr;
>
> // Use HTTP Client with built-in OAuth request handling
> $client = $token->getHttpClient($this->option_array);
>
> // to get Twitter connections
> $client->setUri('
> http://api.twitter.com/1/statuses/followers.xml');
>
> // Set Method (GET, POST or PUT)
> $client->setMethod(Zend_Http_Client::GET);
>
> // Get Request Response
> $response = $client->request();
>
> // Get the XML containing User's Profile
> $content = $response->getBody();
>
> $xmlobj = simplexml_load_string($content);
>
> $scxpath = array(
>
> "tw:source_id"=>"/users/user/id",
>
> "tw:screen_name"=>"/users/user/screen_name"
> );
>
> for($i=1;$i<=count($xmlobj->user);$i++)
> {
> foreach($scxpath as $k=>$v)
> {
> $twitter_con_arr[$k.":".$i] =
> $this->getValue($v,$i-1,$xmlobj);
> }
> $twitter_con_arr['tw:name:'.$i] =
> $twitter_con_arr['tw:screen_name:'.$i];
> $twitter_con_arr['tw:original_source_id:'.$i] =
> $twitter_con_arr['tw:source_id:'.$i];
> }
> return $twitter_con_arr;
> }
>
> --
> 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
