Hey Kallol, Since this is more a shindig question then a partuza related one, you might be interested to know we have a shindig mailing list (see http://incubator.apache.org/shindig/#tab-support for details).
In regards to the RPC service, if a gadget uses a feature that depends on the RPC feature (like settitle, setprefs, dynamic-height), the RPC feature's javascript will also automatically be injected into the gadget html, which will automatically create a RPC channel, what type of RPC channel this is depends on the browser, but for some this means using an iframe. If your interested in the inner workings of this, see the js code at: http://svn.apache.org/repos/asf/incubator/shindig/trunk/features/src/main/javascript/features/rpc/rpc.js If you really want to get rid of those automatically created iframes (which does mean RPC wouldn't work), you could edit your local http://svn.apache.org/repos/asf/incubator/shindig/trunk/features/src/main/javascript/features/rpc/feature.xmland remove the " <script src="rpc.js"/>" from it. -- Chris On Tue, Feb 24, 2009 at 7:04 PM, Kallol Borah <[email protected]>wrote: > > Hi > Thought that making the subject line sound similar to a popular new > movie title may elicit more response :)) > > Now, coming to the real issue, I understand that the client side > container code loads the gadget in an iframe and there is a RPC > mechanism for communicating across the iframe. > > However, what I do not understand is when i retrieve a gadget using > http://abc.com/gadgets/ifr?url=http://xyz.com/mno.xml, why do i still > encounter a hidden iframe that rpc.js creates ? In fact, why is RPC > required in this case at all ?? > > I am desperately trying to get rid of the iframe as a client i am > working on does not support iframes. > > regards > Kallol > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups > "Partuza" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<partuza%[email protected]> > For more options, visit this group at > http://groups.google.com/group/partuza?hl=en > -~----------~----~----~----~------~----~------~--~--- > >
