On Thu, Feb 18, 2010 at 9:48 AM, Sekhar <[email protected]> wrote: > Yeah, the library has its downs, but a lot of the intermittent errors > you see - timeouts, blank results, etc. - are really from Facebook's > side. I've had a rash of these and found a bunch of others having the > same issues, e.g. at > http://forum.developers.facebook.com/viewtopic.php?id=51557. > The latest Facebook problem is with emails (only seeing proxy emails). > All this flakiness keeps me constantly worried about what's going to > break next on Facebook. Do you guys have similar problems?
Oh, I don't blame the library for these issues - they're definitely Facebook's fault. But they're an inherent part of the "undocumented API" of Facebook and we have to live with them if we want to work with the Facebook API. For better or worse, it's the only game in town. You must code defensively, working around what breaks. Something new breaks every week. Does this suck? Yes. Facebook's value is not that it has a stable, consistent, easy-to-use API. I watch my appengine error rates pretty constantly, and when a number goes up, I figure out why and code a workaround - usually a retry for a particular kind of error. This sort of thing is easy to do at the low levels of my simple homegrown client, but difficult to do in a machine-generated library like facebook-java-api. Jeff -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-web-toolkit?hl=en.
