Apologies for not being around to moderate the discussion last week, and thanks to everybody who contributed. To recap, it seems that some folks aren't clear on how fbpylons is different from Facebook's python- sdk. Additional thanks to cd34 for filling in many of the gaps. For completeness, I'll just start from the beginning:
Facebook's python-sdk is an interface for querying and publishing to various attributes of OpenGraph (hence, Facebook) entities. So, for example, it let's you publish to a user's "Wall" or look at a page's "likes." In order to do these kinds of things, though, you first have to obtain an authorization token from the user (or page or whatever). Authorization tokens come in lots of different flavors, each depending on the kinds of permissions the user has granted to your application. The process by which your application obtains a particular flavor of authentication token depends mostly on what kind of application (Connect, Connect/XFBML, Canvas/FBML, Canvas/iframe, etc.) you're writing. Each type has its own weird nuances. (The example given in the python-sdk package is specifically for a Connect/XFBML app, btw.) The major goal of fbpylons would be to establish a unified interface - as in, across the application types and token flavors - for gathering tokens, storing them, and reacting to the many possible authentication states. Again, once you have the appropriately flavored authorization token it's trivial to use python-sdk to manipulate an entity's OpenGraph attributes. Hope that helps. If the problems that fbpylons addresses still seem poorly posed or inadequately motivated, please let me know. Cheers! ~br PS - I won't be around this week either but I'd like to have a design discussion on this thread when I get back, RE: to middleware or not to middleware. On Aug 27, 12:43 pm, cd34 <[email protected]> wrote: > On Aug 27, 4:00 am, eleith <[email protected]> wrote: > > >http://github.com/facebook/python-sdk/ > > From their web site: > > This client library is designed to support the Facebook Graph API and > the official Facebook JavaScript SDK, which is the canonical way to > implement Facebook authentication. You can read more about the Graph > API athttp://developers.facebook.com/docs/api. > > Their library requires you to use the Javascript SDK to get the > tokens. Their example for the App Engine requires it as well. While > the methods do work and it is the library I have used for several > projects, it doesn't handle everything within Python. With an IFrame > canvas, I don't think there is any way to avoid using the Javascript > SDK. > > If you can show an example controller that doesn't use Javascript that > uses Python-SDK, I'd be interested in seeing that. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
