Agreed. You might want to set it to something more like 20. 2 seconds is pretty quick... -Chad
On Thu, Jan 29, 2009 at 3:20 PM, Peter Denton <petermden...@gmail.com> wrote: > I would also try playing with curl_setopt ($curl_handle, > CURLOPT_CONNECTTIMEOUT, 2); > I had issues with that at first. > > On Wed, Jan 28, 2009 at 5:40 PM, dougw <igu...@gmail.com> wrote: >> >> Can you set the CURLOPT_VERBOSE flag to true and capture some >> debugging output? For example: >> >> curl_setopt($curl, CURLOPT_VERBOSE, 1); >> >> Also, how frequently are you attempting to update? And are the >> statuses the same? If you are updating too frequently, Twitter will >> begin to reject the updates. You would know if you are being rejected >> due to this throttling if the status returned by the update method is >> equal to the last successful update. >> >> @dougw >> >> >> On Jan 28, 6:41 pm, "AAfter/ Subhankar Ray" <subhankar....@gmail.com> >> wrote: >> > Greetings, >> > We are using the following code. It does update a couple of times, but >> > not all the time- very unpredictable. What are we missing? >> > ********************* >> > $url = 'http://twitter.com/statuses/update.xml'; >> > >> > // Set up and execute the process curl >> > $curl_handle = curl_init (); >> > curl_setopt ($curl_handle, CURLOPT_URL, "$url"); >> > curl_setopt ($curl_handle, CURLOPT_CONNECTTIMEOUT, 2); >> > curl_setopt ($curl_handle, CURLOPT_RETURNTRANSFER, 1); >> > curl_setopt ($curl_handle, CURLOPT_POST, 1); >> > curl_setopt ($curl_handle, CURLOPT_POSTFIELDS, "status=$message"); >> > curl_setopt ($curl_handle, CURLOPT_USERPWD, "$username:$password"); >> > $buffer = curl_exec ($curl_handle); >> > curl_close ($curl_handle); >> > >> > ****************** >> > Regards, >> > Subhankar Rayhttp://AAfter.Com >
