I'm probably going to be adding functionality to Shindig to control the removal/availability of client-side templating
Do you think this should be done via
A) Optional opensocial-templates-client feature
B) <Param name="client">true|false|{auto}</Param> on
opensocial-templates feature
- where true requests that client code be left in always, false
requests its removal and auto preserves current logic
?
>>> We should probably add a feature to Shindig to always enable client-side
>>> processing.
