7 messages in com.googlegroups.google-picasa-data-apiRe: Timeout errors with Picasa Data API
FromSent OnAttachments
Jon28 Dec 2007 06:56 
Ryan Boyd (Google)28 Dec 2007 08:19 
Jon29 Dec 2007 13:47 
Ryan Boyd (Google)01 Jan 2008 13:14 
Jon05 Jan 2008 08:12 
Ryan Boyd (Google)06 Jan 2008 10:45 
Jon11 Jan 2008 11:31 
Subject:Re: Timeout errors with Picasa Data API
From:Jon (j.@ontri.com)
Date:01/11/2008 11:31:39 AM
List:com.googlegroups.google-picasa-data-api

That did it. I guess it makes sense that a frame acts like embeddible...thanks

On Jan 1, 4:15 pm, "Ryan Boyd (Google)" <api.@google.com> wrote:

Hi Jon,

When the images "don't work", can you tell me what happens? What response code do you receive from the server?

Off of the top of my head, I don't see any problems in the algorithm you're using, but I will followup with some other people to see if there's anything I'm not aware of.

Cheers -Ryan

On Dec 29 2007, 1:47 pm, Jon <j.@ontri.com> wrote:

Hi Ryan -

Thanks for the response. So we get the user's token using the authentication process. Once they select the album they are interested in we get the photo feed for that album. We then make a request using their feed and their token using the code sample below. We parse the XML and store the Image URL in our database for each element in the RSS feed. When the digital frame requests the photos we pass an array of these image URLs to the digital frame. We periodically go back and check Picasa with the same code to see if there are any changes to the album. We then update our table with the array of Image URLs and pass those to the frame later. This process seems to work sporadically. The same exact code shows the photos sometimes and then those same URLs dont work later and then work again. Very bizzare. Should we not be storing the image URLs?

$token = $MYTOKEN; $rssFeed= $RSSFEED; $PicasaAlbums = curl_init();

curl_setopt($PicasaAlbums, CURLOPT_URL, $rssFeed); curl_setopt($PicasaAlbums, CURLOPT_RETURNTRANSFER, true); curl_setopt($PicasaAlbums, CURLOPT_HTTPHEADER,
array('Authorization: AuthSub token="' . $token . '"')); $result = curl_exec($PicasaAlbums);

curl_close($PicasaAlbums);

$xml = new SimpleXMLElement($result);

foreach ($xml->entry as $OneImage) { $URL = $OneImage->content["src"]; storeImageURL($URL); }

On Dec 28, 11:19 am, "Ryan Boyd (Google)" <api.@google.com> wrote:

Hi Jon,

There are no limits which you should be able to hit with normal usage, and there isn't a known issue that I'm aware of.

Can you please explain in more detail what is occurring: a) what feed are you requesting? are you specifying a max-results query parameter to limit it to X results? what other query parameters, if applicable, are you using? b) do you receive a response code from the server? if not- what happens? does the server close the tcp connection, or is the client configured to time out after a specific period of time? how long does it take for thetimeoutto occur?

If you have a packet capture of the HTTP traffic to help us debug, that'd be helpful too. Please remember to remove any auth tokens before posting any packet captures.

Cheers, -Ryan

On Dec 28, 6:57 am, Jon <j.@ontri.com> wrote:

We are using the Picasa API to let a user download pictures from Picasa to their wireless digital photo frames. Once the user authenticates, we use their token to reach in to Picasa on an interval and get the array of images for the album they have selected. The API times out frequently with the exact same code, sometimes it works and sometimes we get an error where the file is not available. We do the exact same thing with Flickr and other sites and it works fine so I don't believe it is anything on our end. Is this a known issue where your serverstimeouton load or do you specifically prohibit a certain