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