[
https://issues.apache.org/jira/browse/WOOKIE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843811#action_12843811
]
Scott Wilson commented on WOOKIE-66:
------------------------------------
There are two APIs that would potentially want to have this kind of call:
OpenSocial has the "getOwner" method, and Wave has the "getHost" method.
In each case this is asking for the person who has some kind of ownership of
the context the widget appears in. However it also assumes that there can only
be ONE owner.
This makes sense in a lot of contexts, such as where a widget is added to a
personal profile page or to a blog.
However there are also contexts where there may be multiple "owners" - for
example in a CMS or collaboration app, there can be multiple users who "own" a
department page. In the case of this Jira tracker, for example, who would
"getOwner()" return? Would it be the issue owner, the project committers?
So while at one level this would be an easy feature to add, it does require a
bit more thinking about the semantics, and how this would be made available in
the connector framework.
> Implement getHost() method of Wave feature
> ------------------------------------------
>
> Key: WOOKIE-66
> URL: https://issues.apache.org/jira/browse/WOOKIE-66
> Project: Wookie
> Issue Type: Task
> Components: Server
> Reporter: Scott Wilson
> Fix For: 0.8.2
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The Wave Gadget API has a getHost() feature that returns the participant that
> added the gadget to the context. Currently this is not implemented; however
> it is a useful feature that ought to be implemented.
> This could be done by:
> - adding a "role" property to the Participant bean with getter and setter
> - adding findHosts(WidgetInstance) static method to Participant
> - updating the database scripts
> In many contexts there can be multiple participants with an "owner" or
> certainly a "manager" role, and we should consider how we might want to
> expose this functionality in the future
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
