It has come up on the turbine-user list that perhaps ContentTool need to have a configurable parameter in TR.props that will determine if URLs will be processed by response.encodeURL() before returning the result back to the template.
This poses the question of how to get that parameter into the pull tool. I would like to propose that we add a second interface for the pull service. This interface would define one method - configure(Configuration). When the PullService is initializing tools and the tool implements that interface, the configure method will be called immediately before init(). The Configuration object would be a subset of the PullService configuration. Specifically, it would be services.PullService.<classname of the pulltool>. As far as the naming of the interface, I was thinking of ConfigurableTool. I was trying to avoid naming conflicts with exisiting Avalon and Stratum interfaces. -------------------------------------------- Quinton McCombs NequalsOne - HealthCare marketing tools mailto:[EMAIL PROTECTED] http://www.NequalsOne.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
