But the session data isn't the hard part.  If you're using pyfacebook,
they are already suggesting that you use the Javascript SDK to handle
auth and just read the session information from there which really
eliminates the need for anything but Javascript/Python.  Your
controller just needs to make sure that it gets/keeps that session
data from page to page, whether internally or through their canvas
methods.  Unless you're still doing FBML, there is very little that
your controller needs to handle beyond making sure there is a valid,
current auth token and one is passed on each FB Canvas pageload,
though, not your IFrame Canvas pageloads.  If you're doing IFrame
Canvas apps, you've already got to use Javascript to handle quite a
few authorization features or write your own popup handlers with the
Facebook look and feel.

Once you have the auth tokens, the wrappers around the Graph API are
fairly developed.

I think what I would like to see is a FacebookController method that
allowed me to pass in my app id, secret, key, desired permissions etc.
and would handle that transparently.  My actions would then know the
fb_uid for each request, and perhaps could have a method defined that
would pass a variable to each action that contained my local session
info.  At that point, I can concentrate on the app without worrying
about other methods.  When the graph API fails due to permissions, a
handler in the Controller could optionally prompt the user to add
additional permissions and carry the action through.  Passing
information through the Invites/Friend Tagging so that referrals could
be tracked would also be nice.  Having the controller or attached
methods generate properly formed urls and messages to handle those
tasks would be nice.

As for FBConnect, I believe Velruse handles many different OpenID/
similar authentication systems, but, still needs a backend hook
through repoze or something similar.  I could be wrong.

-- 
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.

Reply via email to