You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Henry Saputra (Updated) (JIRA)" <ji...@apache.org> on 2012/01/19 20:50:40 UTC

[jira] [Updated] (SHINDIG-1678) The flash transport to support RPC for IE7 has problem with multiple gadgets in a single container

     [ https://issues.apache.org/jira/browse/SHINDIG-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henry Saputra updated SHINDIG-1678:
-----------------------------------

    Summary: The flash transport to support RPC for IE7 has problem with multiple gadgets in a single container  (was: The flash transport to support RPc for IE7 has problem with multiple gadgets in a single container)
    
> The flash transport to support RPC for IE7 has problem with multiple gadgets in a single container
> --------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1678
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1678
>             Project: Shindig
>          Issue Type: Bug
>          Components: Javascript 
>    Affects Versions: 2.0.2, 3.0.0
>            Reporter: Henry Saputra
>            Assignee: Henry Saputra
>              Labels: ie7, rpc
>
> The flash rpc transport to support ie7 does not work properly for multiple gadgets in a single container. The function flushHandshakes in flash.transport.js only called by ready() function which only be called once by the flash component after it initialized itself.
> The flash component act as singleton to make sure the main function only called once for a page. The transport ready() function which called at the end of the main function of the actionscript file hence only called once even though multiple gadget call gadgets.rpc.setupReceiver().
> So if a second gadget is in the same container, the flushHandshakes() will never be called to setup that gadget iframe.

--
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