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

Javier Pedemonte commented on SHINDIG-1330:
-------------------------------------------

STATUS OF LATEST PATCH (SET #4)
* Adds new pubsub-2 feature.
* Adds the following new APIs:
    - gadgets.byId()
    - gadgets.rpc.config()
            - For setting config parameters on rpc connection. Right now only
               takes a security callback.
    - gadgets.rpc.removeReceiver()
    - gadgets.rpc.getReceiverOrigin()
* Updated NIX transport to support parent verification, given a valid relay 
file.
* Updated WPM transport to check origin on message reception. Also added checks 
for non-async WPM and Opera 9.x's use of "event.domain" instead of 
"event.origin".
* Hook for possible frame phishing in rpc.js, given a valid relay file.
    
QUESTIONS/REMAINING ISSUES
* Not sure of the best place to put gadgets.byId(). For now, I've put it in 
core.util/util.js, but that needs to be fixed.
* In shindig-container.js, since OpenAjax Hub creates the iframe, needed to 
split code up into two cases: the case where gadget requires the 'pubsub-2' 
feature and therefore uses OAA Hub to create and manage the iframe; and the 
existing case where the iframe is created in shindig-container.js. This code 
isn't pretty, since I need to do a metadata request for the gadget. Ideally, I 
should be using the new container code (the 'shindig.container-1.0' feature), 
since it fetches and caches the gadget metadata on the container side. Will 
this new container code be the default container for Shindig 2.0?
* Not sure about gadgets.rpc.config(). Need a way to set the security callback 
function. In a previous discussion, we decided to go with config() rather than 
a function specifically for the callback (see 
http://wiki.opensocial.org/index.php?title=PubSub.next_Proposals#Secure_rpc), 
since we could expand it in the future for other uses.

> Incorporate OpenAjax Hub as Pub-Sub Mechanism for Shindig (Open Social 1.next)
> ------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1330
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1330
>             Project: Shindig
>          Issue Type: Bug
>          Components: Javascript 
>    Affects Versions: 2.0.0
>         Environment: Shindig trunk.
> Java 5
> Windows
> FireFox, Safari, Chrome
>            Reporter: Han Nguyen
>             Fix For: 2.0.0
>
>         Attachments: pubsub2.patch
>
>
> This patch is an initial alpha implementation by Javier Pedemonte 
> (OpenAjaxHub/IBM) based on the proposal described here
> http://wiki.opensocial.org/index.php?title=Incorporate_Open_Ajax_Hub_as_Pub-Sub_Mechanism_for_OpenSocial_1.next
> While there are still more work, the patch provides a new pubsub feature 
> which uses OAHub as the underlying eventing model. 
> The /content/container/sample-pubsub-2.html demonstrates a simple pubsub 
> example using the feature.
> API documentation can be found in the comments of the 
> /javascript/features/pubsub-2/pubsub-2.js

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

Reply via email to