Migrating a Facebook application to Bebo

John Maver
Written by John Maver  ()
on July 27, 2018 ·

Doorbell_banner

Recently, we created a Bebo version of our Doorbell application for Facebook.

Here is what I did:

  1. created a new app using the developer app. Used a new callback location.
  2. Updated my db to handle the larger sized userid and sessionkeys
  3. updated web server to handle the new callback location
  4. forked my fb source code to a new Bebo version
  5. included the new Bebo PHP library in my source files
  6. Change all $fb = new Facebook($apikey, $appsecret) to $bebo = new Bebo($apikey, $appsecret)
  7. Change all $fb->api_client calls to just $bebo-> calls, and manually tweaked the parameters to be associative arrays.
  8. Change all FBJS code to mock Ajax, where it can be, or remove otherwise
  9. go through each code path with tracing to figure out what bebo doesn't implement or implements differently.

What is nice, is that most of it just works. The tools are the same, the fb_* post variables are there. They just don't have complete parity with FB on the whole API yet, but they seem to be working on it.

The big gotchas are:

  1. The add method isn’t the same. On Bebo, it seems like a user must add your application to interact with it, and that add happens without any calls to your code. There is therefore less to handle in terms of user state than Facebook.
  2. The api calls are different. Facebook provides a nice wrapper for their REST implementation, and Bebo doesn’t have the same level of completeness in theirs. My next task is to write the same wrapper for Bebo.
  3. All callback parameters via Ajax are sent as POSTs rather than GETs regardless of how they are specified in the call.

Topics: Programming

Follow us:

Enjoy this article? Don't forget to share.

Interested in Working With Us?

Click Here to Find Out More About How We Can Help You