Thanks Lukas - I missed it - the params are passed to AssetsHelper. So, the assets *do* become absolute, but only if you have specified at least one "assets_base_urls" (it's an array - the Templating engine picks from multiple base urls randomly, but consistently for a given asset path).
So, is that the solution or should you simply be able to render the path "absolutely" as Jordi mentioned without needing assets_base_urls. I think allowing it to be absolute, and then if it's not absolute letting assets_base_urls take over makes sense. Ryan Weaver Lead Programmer - iostudio - Nashville, TN http://www.iostudio.com http://www.thatsquality.com Twitter: @weaverryan On Fri, Jan 7, 2011 at 8:20 AM, Lukas Kahwe Smith <[email protected]>wrote: > > On 07.01.2011, at 15:14, ryan weaver wrote: > > > Hey guys > > > > Hasn't there been conversation somewhat related to this before per having > assets at different CDN's? Looking, I see the templating configuration > parameter "assets-base-urls", which ultimately sets a parameter on the DIC > called "templating.assets.base_urls". But, I don't see this being used > anywhere. Can anyone else shed some light? > > It is used by the asset helpers that have now been moved to the bundle. The > list of urls are IIRC just a list of CDN's for the same assets. I was > looking to get support for multple CDN's with different content (aka my own > CDN for my own stuff and Google AJAXAPI for YUI etc.). > > regards, > Lukas Kahwe Smith > [email protected] > > > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
