Paul Covell

For completeness, it seems that if I were able to get ahold of the facebook signed_request parameter from the login, I would be able to use that directly with the...

e915882bcbc610a526b604a8d5bdf69aa1c489ee

Any thoughts here?

Sure, the request looks like this: ``` client_id:... client_secret:... grant_type:assertion assertion_type:facebook.com assertion:AAADh2hKj0ZAUBALSvzY7HB3CIb0Y0ZAOB82bFZBvBCBGsZBOUTtM9dfZAbEc3YX9NHE0HvXmauQ26prlbh670Iab2vqNm1aId624t7QvqbQZDZD ``` It serves the same purpose as sending the signedRequest from Facebook, except in this case the Facebook...

Brian, I'd like to understand more why it's not secure, provided I send the token over an HTTPS link. I'd of course like to make sure I am roughly within...

@edgar I've added comments on Issue #21, please review and let me know if anything is missing -- then it will be easy to wrap up any loose ends and...

@aseemk, can you be more specific about where you ran into the problem? I agree that the 'current resource' ID should always be 'id'. But, if you are nested, then...

Are you referring to rails-style route helpers? Along the lines of: /** - resource: lists @ /lists - 1. lists_path() === /lists - 2. list_path(list) === /lists/ - 3. edit_list_path(list)...

If we write the functions to construct a route from the resource, those can be useful in both the view and the controller: - Controller: res.redirect(list_path(list)) - View (Jade format)...

japj, if I understand you correctly, you are actually using two segments of the path to identify a unique resource (foo+bar), and that is how your example differs from mine,...