Closed GoogleCodeExporter closed 8 years ago
I have a feeling, that we should just get rid of isDesktop(). If it's just
there for
early-failure. I would much rather send the request to facebook ( since their
policies change all the time, let them send an exception ). It would make our
life
much easier.
I am even leaning towards removing SessionSecret... sort-of. Since really all
we
need is the "CurrentSecret", we don't care how we got it. If we got it through
auth_getSession, or through a config file. :)
Just wondering if storing how we got the sessionSecret, and storing the original
sessionSecret might be useful later.. but I think for most things, it's not.
Less things to confuse us and users in the long run. Ideas?
Original comment by fern...@gmail.com
on 12 Mar 2009 at 3:50
Note: We can automatically detect whether we have a "session secret" vs. a
normal
secret because session secrets all end in 2 underscores __
Original comment by david.j....@googlemail.com
on 18 Mar 2009 at 9:16
I won't be doing any checkins on this one for a long time anyway... The
functionality
doesn't work as documented.
http://forum.developers.facebook.com/viewtopic.php?pid=132736
Original comment by david.j....@googlemail.com
on 18 Mar 2009 at 9:18
Finally fixed by working out that you have to specifically set the application
to
desktop mode before it will understand session secrets.
http://code.google.com/p/facebook-java-api/wiki/DesktopMode
Note that I've removed the setIsDesktop(boolean) method. This was misleading.
Instead, use auth_getSession( true ) to tell the client to generate a session
secret
for you.
Original comment by david.j....@googlemail.com
on 26 Mar 2009 at 10:52
Original comment by david.j....@googlemail.com
on 26 Mar 2009 at 10:52
very nice! It works great
Original comment by mclaughl...@gmail.com
on 30 Apr 2009 at 4:12
Original issue reported on code.google.com by
david.j....@googlemail.com
on 12 Mar 2009 at 11:18