I'm using facebook-java-api for an app that's about to go into production for Android and GWT. I thought the API was simple/clean, very easy to use tokens (for Android logins) and session, and has some useful extras like verifying session signature. Also, you can get the source (I've in fact addded an API call that's missing).
@Jeff, why do you think it's horrid? Just wondering if there's something I need to know before putting this in production. On Feb 12, 11:36 am, Jeff Schnitzer <[email protected]> wrote: > On the server side, throw facebook-java-api in the trash. It's > horrid. The Facebook API, while kludgy as hell, is actually pretty > straightforward. Just make HTTP requests and parse the results with > your favorite JSON or XML parser (I use Jackson). -- 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.
