I'm not sure what you mean by "changing the gadget module". What I meant for (B) was support for
<Require feature="opensocial-templates"> <Param name="client">true</Param> </Require> as a way of preventing Shindig from stripping away client-side templating support as an optimization. You could also do <Require feature="opensocial-templates"> <Param name="client">false</Param> </Require> if you are sure you won't need client templating. "auto" would be the default value which would mean Shindig would try to use some heuristics to see if client templating should be left in. On Tue, May 5, 2009 at 2:00 PM, Jordan Zimmerman <[email protected]> wrote: >>A) Optional opensocial-templates-client feature >>B) <Param name="client">true|false|{auto}</Param> on >>opensocial-templates feature > > For (B) do you mean changing the gadget module? If so, then I think this > is a very bad idea. I vote for (A). > > Jordan Zimmerman > Principal Software Architect > 831.647.4712 > 831.214.2990 (cell) > [email protected] > > SHOP*COMTM > Shop Smart, Save Big(tm) > www.shop.com > > This message (including any attachments) is intended only for > the use of the individual or entity to which it is addressed and > may contain information that is non-public, proprietary, > privileged, confidential, and exempt from disclosure under > applicable law or may constitute as attorney work product. > If you are not the intended recipient, you are hereby notified > that any use, dissemination, distribution, or copying of this > communication is strictly prohibited. If you have received this > communication in error, notify us immediately by telephone and > (i) destroy this message if a facsimile or (ii) delete this > message > immediately if this is an electronic communication. > > Thank you. >
