[jira] Commented: (SHINDIG-558) Unify signed fetch and OAuth

["Kevin Brown (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SHINDIG-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627599#action_12627599 ] 

Kevin Brown commented on SHINDIG-558:
-------------------------------------

Some other things that would be nice to clean up here:

- Make sure that the container is always present throughout the stack, to make it easier to discriminate requests (for logging, tracking, error reporting, and code path switching). I tried to do this by attaching it to HttpRequest, but it's missing a few pieces.

- Get rid of this:
   * Get Factory from provider
   * Get Fetcher from Factory
   * Get response from Fetcher.

That can really just be:
   * Get response from Fetcher.

I want to make sure that extensibility is thought about as well. As you know, integrating custom signed fetch behavior is painful right now. Container-provided parameters would be tremendously useful.




> Unify signed fetch and OAuth
> ----------------------------
>
>                 Key: SHINDIG-558
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-558
>             Project: Shindig
>          Issue Type: Bug
>          Components: Gadget Rendering Server (Java)
>            Reporter: Brian Eaton
>         Attachments: unify.patch
>
>
> Goal #1: implement the OAuth for social sites proposal discussed on the spec list.
> Goal #2: get HMAC support for signed fetch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.