On Oct 9, 2011, at 17:54 , Lukas Kahwe Smith wrote: > > On Oct 9, 2011, at 17:51 , Johannes wrote: > >> Maybe we need to implement the routing system a bit closer to the HTTP >> spec, so that it does more content negotiation than just relying on >> the url/method? >> >> That would not only solve the problem for versioning, but also the >> problem that different controllers might consume/produce different >> media types. > > > Yeah, that would be another option. In general I tried to not mess at this > level to not make the implementation of different matchers too hard, then > again for example I am sure that with apache there is some module one could > use to help somehow ..
I will have a look if I can get things to work implementing the following algorithm in PHP: http://httpd.apache.org/docs/2.2/content-negotiation.html As well as trying to integrate all of this with the Apache URL Matcher. We can then later see if we move this to core or keep it as extensions in the FOSRestBundle. 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] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
