FacebookWebappHelper support for profile pages - concept of knowing page owner user but not page viewer user.

[GoogleCodeExporter]

Currently FacebookWebappHelper doesn't work for profile pages (or boxes
with the newer Facebook integration points). When loading a profile page,
you don't get passed the same parameters. Instead, Facebook passes a
different parameter to tell you who's profile page it is, not who's viewing it.

This doesn't seem to make sense at first, but the reason it does this is to
avoid confusion in the scenario where Adrian is viewing Brian's profile
page. We want to display information for Brian (it's Brian's profile!) but
Adrian is actually the logged in user.

So, Facebook handles this by using different parameters so that you have to
know what you're doing in order to use the feature. Facebook doesn't even
tell you that it's Adrian viewing the page; all you know is that it's
Brian's page.

Let's extend FacebookWebappHelper with methods to allow Java apps to work
on profile pages. The helper needs to detect and fetch the separate
parameters and set a "profilePage" boolean so that we know that we're in
the profile situation. I need to examine the scenario where a user is
looking at their own profile. Is that a different workflow to some other
user looking at the user's profile?

Original issue reported on code.google.com by david.j....@googlemail.com on 13 Jan 2009 at 12:53