Hi Stanton: The description of browser support is in each of the *.transport.js files: http://svn.apache.org/repos/asf/shindig/trunk/features/src/main/javascript/features/rpc/
It's relatively complete, but since the lib has evolved over time it can be summarized pretty easily: 1. window.postMessage for most browsers. 2. If enabled, Flash for everything else. 3. Otherwise, FE for FF2; RMR for others. I've always tested with rpctest_container.html. Note that this harness doesn't test the "new" use cases such as direct parent <-> grandchild or sibling <-> sibling communication. --j On Wed, Jun 22, 2011 at 8:54 AM, Stanton Sievers <[email protected]>wrote: > Hi all, > > I'm investigating a change to Shindig's RPC layer to allow the container > script to load in a separate frame than that of the container content, > i.e., the frame in which we render the gadget iframes. The RPC layer has > several transports to support different browsers. I have two questions: > > Is there a statement somewhere of what browsers are supported by Shindig > or Shindig's RPC? The rpc feature source documentation indicates browser > versions but I'm not sure if this list is complete. > > What is the best way to test the RPC layer? I see that a test container > exists at /container/rpctest_container.html and this is what I've been > using to test my preliminary changes to rpc.js and wpm. > > Thanks, > -Stanton > >
