Are you volunteering to be the maintainer of the pylons-facebook extension? :)
Given that I am a Pylons novice at this point, I can probably commit
to hacking some stuff together. If you can lower the barrier for
entry into pylonsext, I'm in. ;-)
Cheers!
~br
--
You received this message
On Aug 23, 2010, at 6:07 PM, BrianTheLion wrote:
At this point in my effort, though, certain questions about the
overall design of fbpylons and its approach to solving the problems at
hand are starting to surface. Hence, my interest in soliciting
feedback and help from others who have also
This notion of implementing fbplyons as middleware comes from the
original Facebook-for-Python implementation, pyfacebook. As a package,
it provided WSGI middleware that put a facebook object in the
request's environment that a programmer could talk to without having
to deal with all those ugly
Parts of the REST API are still required and preloading FQL is another
issue that needs to be addressed.
While decorated actions make sense, I find that I almost have an all
or nothing situation with a controller. The one loophole that used to
be present with facebook was closed in June
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
One thing I seriously debated was whether a single Pylons instance
would be used per app, or, whether a single Pylons instance would have
multiple controllers, each handling a separate Facebook application.
Currently, I have one Nginx with uWsgi (4 threads on a quadcore) that
talks to a single
http://github.com/facebook/python-sdk/
works wonderfully. uses open auth 2 protocol to authenticate users,
implements most of open graph api and some forks added in original api
and fql api. overall, the library is very easy to build on, and i have
one integrated into my pylons app and it does
On Aug 27, 4:00 am, eleith ele...@gmail.com 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
I've done a lot of cross-language systems. They're really quite easy.
The main issue with them is session data, but everyone can read YAML
and JSON. while they're not as fast as natively pickled/packed data,
even the slowest systems around can process them with ease.
--
You received this message
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
i tried it a while back, and then gave up.
i don't think its worth it, because facebook has changed the way the
apps work so many damn times
i think you'd be better off just using one of the many full-featured,
mature, has-tons-of-people-maintaining-it php libraries that are out
there , and let
://github.com/brianthelion/fbpylons.
My goal was to build a drop-in, It Just Works! (tm), Swiss-army-
knife of a support package for, well, building Facebook apps using
Pylons.
Requirements:
1) Handle the spectrum of Facebook application types (Connect, Connect/
XFBML, Canvas/FBML, Canvas/iframe
in collaborating, here's my
very modest (and poorly documented) start:
http://github.com/brianthelion/fbpylons.
My goal was to build a drop-in, It Just Works! (tm), Swiss-army-
knife of a support package for, well, building Facebook apps using
Pylons.
Requirements:
1) Handle the spectrum of Facebook
-in, It Just Works! (tm), Swiss-army-
knife of a support package for, well, building Facebook apps using
Pylons.
Requirements:
1) Handle the spectrum of Facebook application types (Connect, Connect/
XFBML, Canvas/FBML, Canvas/iframe, etc.)
2) Minimize the number of insertion points. (Ideally, drop
14 matches
Mail list logo
