requestSendMessage - why is this an RPC call to the container (web page)

[Justin Wyllie <ju...@hotmail.co.uk>]

Hi
In Shindig if a gadget makes a requestSendMessage call this is handled in container.js and it uses RPC to forward the request to the containing web page; a bit like adjustHeight or setTitle.
I'm trying to understand why this call would be sent to the containing web page. Surely it is the backend which would handle messaging - so I would have expected this to be  a JSON-RPC call like say writing app data.
Is there any reason it has been done this way?
with thanks
Justin  		 	   		  
_________________________________________________________________
http://clk.atdmt.com/UKM/go/195013117/direct/01/
We want to hear all your funny, exciting and crazy Hotmail stories. Tell us now

Re: requestSendMessage - why is this an RPC call to the container (web page)

[Kam Kasravi <kk...@yahoo-inc.com>]

makeRequest is reserved for requests that are backend bound. Although I haven't looked at the documentation,
perhaps this is a request to route to another gadget via the container. This type of functionality would certainly 
be needed.

kam

On Jul 2, 2010, at 4:51 AM, Justin Wyllie wrote:

> 
> Hi
> In Shindig if a gadget makes a requestSendMessage call this is handled in container.js and it uses RPC to forward the request to the containing web page; a bit like adjustHeight or setTitle.
> I'm trying to understand why this call would be sent to the containing web page. Surely it is the backend which would handle messaging - so I would have expected this to be  a JSON-RPC call like say writing app data.
> Is there any reason it has been done this way?
> with thanks
> Justin  		 	   		  
> _________________________________________________________________
> http://clk.atdmt.com/UKM/go/195013117/direct/01/
> We want to hear all your funny, exciting and crazy Hotmail stories. Tell us now