Georg, The FileLoader class (within Routing component) already supports this, as it aggregates the PHP, XML and YML loaders. When it receives a resource string, it will iterate across the three file loaders and delegate to whichever says "yes, I support that resource string". The logic for support is as easy as checking the file extension in this case.
I anticipate supporting "file" as a loader option, which will use the above behavior (current default for Symfony2) and explicit loaders such as "yml", which would directly delegate to YamlFileLoader. Are you asking whether it makes sense to default to loader="file" if none was specified? On Thu, Dec 2, 2010 at 5:53 PM, Georg <geor...@have2.com> wrote: > I don't think that it is too verbose. In your xml example it is obvious > that a xml file is the resource, but which loader understands the xml > content of this file must be specified. > IMO the protocol/loader should be specified like already in use > everywhere, with :// as separator. And the url needs only to be > understood by the loader, for example > > dbsecurityloader://mysql://username:passw...@database/table > > should be considered valid (Or maybe it should be url-encoded???). > > -- jeremy mikola -- 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
