[
http://jira.amdatu.org/jira/browse/AMDATU-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11117#comment-11117
]
Ivo Ladage - van Doorn commented on AMDATU-236:
-----------------------------------------------
Shindig contains its own oAuth server, but since we want to support oAuth
without the need of OpenSocial stuff, an implementation has been added to
Amdatu. I'm not sure if we can really 'remove' the oAuth server from shindig,
as shindig is not really a composite framework.
The reason that Shindig uses net.oAuth is that it associates gadget URLs with
consumer keys (it registers each gadget as service consumer). It makes sense to
do this, so I guess the only thing to do here is not exporting the net.oauth
package.
> The Shinding bundle exports the OAuth API, except for net.oauth.http
> --------------------------------------------------------------------
>
> Key: AMDATU-236
> URL: http://jira.amdatu.org/jira/browse/AMDATU-236
> Project: Amdatu
> Issue Type: Question
> Components: Amdatu Auth
> Reporter: Angelo van der Sijpt
> Fix For: 0.2.1
>
>
> Since the introduction of OAuth, the Shindig bundle gained a dependency on
> OAuth. It packages most of OAuth itself, creating two exporters of most of
> the OAuth packages, which in itself is not a problem. However, the Shindig
> bundle does _not_ export net.oauth.http. This can be an oversight, a
> deliberate decision, or a point for discussion.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
