[
https://issues.apache.org/jira/browse/SHINDIG-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Baxter updated SHINDIG-1709:
---------------------------------
Description: If you enable RPC arbitration in a container and you want to
allow a set of RPC service ids regardless of whether the gadgets has features
that uses them, it is very difficult to do so. The only way to do this today is
to provide your own arbitrator function to the common container. Essentially
this function will do the same thing as the default implementation in the
common container except have a list of allowed RPC service ids. It be easier if
containers could specify a list of additional RPC services to allow on a per
gadget basis. It would also be nice if this was integrated into the gadget
admin feature in Shindig already. (was: If you enable RPC arbitration in a
container and you want to allow a set of RPC service ids regardless of whether
the gadgets has features that uses them, it is very difficult to do so. The
only way to do this today is to provide your own arbitrator function to the
common container. Essentially this function will do the same thing as the
default implementation in the common container except have a list of allowed
RPC service ids. It would be much easier for consumers of the common container
to supply a list of allowed RPC service ids for this container in the config.)
> The RPC abritration code in the common container should allow you to pass in
> a list of allowed RPC services for that container.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SHINDIG-1709
> URL: https://issues.apache.org/jira/browse/SHINDIG-1709
> Project: Shindig
> Issue Type: Improvement
> Reporter: Ryan Baxter
> Attachments: issue-1709.patch
>
>
> If you enable RPC arbitration in a container and you want to allow a set of
> RPC service ids regardless of whether the gadgets has features that uses
> them, it is very difficult to do so. The only way to do this today is to
> provide your own arbitrator function to the common container. Essentially
> this function will do the same thing as the default implementation in the
> common container except have a list of allowed RPC service ids. It be easier
> if containers could specify a list of additional RPC services to allow on a
> per gadget basis. It would also be nice if this was integrated into the
> gadget admin feature in Shindig already.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
