That makes a lot of sense. Thanks Bruno and Kevin for the clarifications. Chak
On 1/27/08 11:51 PM, "Bruno Bowden" <[EMAIL PROTECTED]> wrote: > The point about rpc is that we can improve the underlying implementation > over time. The big changes will be when get confident enough with Caja to > remove the iframe. At that point we don't need inter-frame communication at > all. > > On Jan 26, 2008 10:16 AM, Kevin Brown <[EMAIL PROTECTED]> wrote: > >> gadgets.rpc is the standard way of abstracting implementation details like >> ifpc. Very soon someone (either myself or Zhen most likely) will be >> refactoring libraries that use ifpc to instead use rpc. >> >> All new features should be built around rpc. Implementations (including >> shindig) are free to implement rpc in any way that they like. >> >> On Jan 25, 2008 8:42 AM, Chak Nanga <[EMAIL PROTECTED]> wrote: >> >>> Hi, >>> >>> What is the purpose of the newly added ³rpc² feature since some of the >>> gadget<--->container and gadget<--->gadget communication functionality >>> seems >>> to be available via ifpc? >>> >>> Thanks >>> Chak >>> >>> >>
