Not sure if i am pestering you guys, but i dont have any other option... :-(

I am also invoking
gadgets.rpc.setRelayUrl(iframeId, iframeUrl, false);
 gadgets.rpc.setAuthToken(iframeId, rpcToken);

from the container for each gadget generated.

and alert from nix.transport.js

call: function(targetId, from, rpc) {
      try {
        // If we have a handler, call it.
        alert(targetId+" = "+nix_channels[targetId]+" from "+from+" rpc is
"+gadgets.json.stringify(rpc));
       ....
    }

gives


.. = from remote_iframe_0 rpc
{"s":"set_title","f":"remote_iframe_0","c":0,"a"["Account
overview"],"t":"0.6466592220939002","I":false}

works (once in a blue moon)

.. = undefined from remote_iframe_2 rpc is
{"s":"set_title","f":"remote_iframe_2","c":0,"a":["Account
summary"],"t":"0.33673688496145","I":false}

doesnt work

I don't understand why most of the times the undefined comes up and then it
fails...


Please , all those gurus and experts, any tip, something i might be
missing...

Thanks and Regards,
Hafiz

2009/11/18 Hafiz A Haq <[email protected]>

> I have also added rpctoken into the iframeurl like
>
> https://
> .../ifr?container=...&lang=en&country=US&view=default&nocache=1&rpctoken=0.9956869901138398,
> which is essentially a random number
>
> still the rpc calls are not getting through.
>
> Anything else i might be missing.
>
> 2009/11/18 Hafiz A Haq <[email protected]>
>
> Any input would help me. Please provide a hint why nix transport fails when
>> container and shindig is at 2 different secure domains?
>>
>> 2009/10/28 Hafiz A Haq <[email protected]>
>>
>>> Seems there is something that makes the nix transport mechanism fail
>>> here, the call method is not going through , where it fails at the check
>>> if (nix_channels[targetId])
>>>
>>> In the call method the parameters targetId, from, rpc alerts to
>>>  '.. , remote_iframe_3 , [object Object]'
>>>
>>> Can anyone please give me a hint why the code
>>>
>>> if (nix_channels[..])
>>>
>>> is not going through as expected..
>>>
>>> Any help is appreciated.
>>>
>>> Thanks and REgards,
>>> Hafiz
>>>
>>> 2009/10/28 Hafiz A Haq <[email protected]>
>>>
>>> Hi All,
>>>>
>>>> My dashboard application is up and running in production, thanks to
>>>> Shindig and you guys. Due to some serious mistake from QA and IT guys i 
>>>> have
>>>> a bug at this last hour as rpc feature is broken in production and my
>>>> clients are not so happy.. :(
>>>>
>>>> In production each client has individual subdomains and shindig is
>>>> deployed in a common subdomain for all customers, both over https. RPC is
>>>> now broken in IE6,7 and setTitle, setHeight ... are not working.
>>>>
>>>> I assigned gadgets.parent in myContainer.js with a regex pattern like
>>>>
>>>> "gadgets.parent" : "(https://localhost:8443|
>>>> https://customer1.app.company.com|https://customer2.app.company.com)",
>>>>
>>>> and rpc like
>>>>
>>>>  "rpc" : {
>>>>     // Path to the relay file. Automatically appended to the parent
>>>>     // parameter if it passes input validation and is not null.
>>>>     // This should never be on the same host in a production
>>>> environment!
>>>>     // Only use this for TESTING!
>>>>     "parentRelayUrl" : "/app/core/main/rpc_relay.html",
>>>>
>>>>     // If true, this will use the legacy ifpc wire format when making
>>>> rpc
>>>>     // requests.
>>>>     "useLegacyProtocol" : false
>>>>   }
>>>>
>>>> Now i tried
>>>>
>>>> var parentRelayUrl = window.location.protocol + "//" +
>>>> window.location.host
>>>> gadgets.container.setParentUrl(parentRelayUrl);
>>>>
>>>> from the container js file, which is loaded after loading all required
>>>> shindig js file dependencies. Still i am not able to get the rpcs to work
>>>> properly in IE6,7. Any help is greatly appreciated as some of my customers
>>>> are tied down on IE7.
>>>>
>>>> Best Regards,
>>>> Hafiz
>>>> --
>>>> He who asks is a fool for five minutes, but he who does not ask remains
>>>> a fool forever.
>>>>
>>>
>>>
>>>
>>> --
>>> He who asks is a fool for five minutes, but he who does not ask remains a
>>> fool forever.
>>>
>>
>>
>>
>> --
>> He who asks is a fool for five minutes, but he who does not ask remains a
>> fool forever.
>>
>
>
>
> --
> He who asks is a fool for five minutes, but he who does not ask remains a
> fool forever.
>



-- 
He who asks is a fool for five minutes, but he who does not ask remains a
fool forever.

Reply via email to