[cvs] [Wiki] changed: Doc/Dev/Horde_Service_Facebook

Michael Rubinsky mrubinsk at horde.org
Sun Mar 1 15:39:39 UTC 2009


mrubinsk  Sun, 01 Mar 2009 10:39:38 -0500

Modified page: http://wiki.horde.org/Doc/Dev/Horde_Service_Facebook
New Revision:  1.6
Change log:  You create objects, not classes

@@ -132,9 +132,9 @@
  </code>

  ++ Doing Something Useful - Calling API Methods

-The various API calls are seperated into various classes according to  
the part the Facebook API your interacting with. For example, as you  
may have noticed that most of the methods we have used so far have  
been in the Horde_Service_Facebook_Auth class.  The  
Horde_Service_Facebook object will lazy load the object that you need,  
so you don't have to worry about creating these classes yourself.  
There are some things to be aware of before querying any data from a  
user's Facebook account. First, you absolutely need to be familiar  
with Facebook's policies on data usage. There are restrictions on what  
can be shown to users, what can be stored locally and for how long, as  
well as other issues. You can read more at  
http://wiki.developers.facebook.com/index.php/Platform_Policy.  You  
will also find that there are often times more then one way to obtain  
information. You can make normal API calls or you can use the Facebook  
Query Language (FQL) a query language **very** similar to SQL.  It is  
often time more efficient to obtain the data you are after using FQL  
then to use API calls - especially when multiple API calls would be  
necessary.  In fact, a number of Facebook's API calls are actually  
just thin wrappers around the matching FQL query. See  
http://wiki.developers.facebook.com/index.php/FQL for more information  
on FQL and see the section below on FQL to see how to make these  
queries using this library.
+The various API calls are seperated into various classes according to  
the part the Facebook API your interacting with. For example, as you  
may have noticed that most of the methods we have used so far have  
been in the Horde_Service_Facebook_Auth class.  The  
Horde_Service_Facebook object will lazy load the object that you need,  
so you don't have to worry about creating these objects yourself.  
There are some things to be aware of before querying any data from a  
user's Facebook account. First, you absolutely need to be familiar  
with Facebook's policies on data usage. There are restrictions on what  
can be shown to users, what can be stored locally and for how long, as  
well as other issues. You can read more at  
http://wiki.developers.facebook.com/index.php/Platform_Policy.  You  
will also find that there are often times more then one way to obtain  
information. You can make normal API calls or you can use the Facebook  
Query Language (FQL) a query language **very** similar to SQL.  It is  
often time more efficient to obtain the data you are after using FQL  
then to use API calls - especially when multiple API calls would be  
necessary.  In fact, a number of Facebook's API calls are actually  
just thin wrappers around the matching FQL query. See  
http://wiki.developers.facebook.com/index.php/FQL for more information  
on FQL and see the section below on FQL to see how to make these  
queries using this library.
  +++ Horde_Service_Facebook_Users
  <code type="php">
  $success = $facebook->users->setStatus('playing around with the  
Horde_Service_Facebook library again.');
  </code>



More information about the cvs mailing list