Thanx Jeff, i filed a bug about this issue:

http://code.google.com/p/gdata-issues/issues/detail?id=799


On 24 sep, 23:54, "Jeff Fisher (Google)" <[EMAIL PROTECTED]>
wrote:
> Wow, that's pretty terrible latency. You should file a bug about that:
>
> http://code.google.com/p/gdata-issues/issues/list
>
> Use the <updated> element of the feed to determine if the feed has
> changed since you cached a copy.
>
> Cheers,
> -Jeff
>
> On Sep 24, 1:03 pm, Gummbahla <[EMAIL PROTECTED]> wrote:
>
>
>
> > I'm currently working on a project in which i'm using the Picasa Web
> > Albums PHP API. Although everything works fine, i was wondering why it
> > takes such a long time for requests to be completed.
> > In my little test, i'm first connecting to Google through the API.
> > Then i'm retreiving all user albums from two different users (say x
> > and y). X has about 25 albums, Y has only 2 albums.
> > I did some analysis on the amount of time each step consumes (the
> > number is the total amount of time up till then):
>
> > Starting: 0
> > Connected to Google API: 0.75138092041016
> > Retreived userfeed xxxxxxx: 1.8700640201569
> > Retreived userfeed yyyyyyy: 2.3094940185547
> > Done!: 2.3114068508148
>
> > As you see, it takes almost 2,5 seconds to retreive the album lists of
> > only 2 userfeeds. Because this is not acceptable for my application, I
> > thought of caching possibilities. However, how do i determine whether
> > my cache is outdated without the need for downloading the whole
> > albumlists to compare everything?- Tekst uit oorspronkelijk bericht niet 
> > weergeven -
>
> - Tekst uit oorspronkelijk bericht weergeven -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Picasa Web Albums API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Picasa-Data-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to