Hey there, Symfony2 devs! I have a couple of topics for the upcoming IRC discussion, that I'd like to get your feedback on and see if they make sense.
RESTful view handling: In rest URI represents a resource. One resource - one URI. So /users/1 is actually a different resource from /users/1.xml or /users/1.json I know that this is the most common way of providing RESTful routes, but its semantically incorrect. Having seen a couple of presentations of modern REST architectures, the most common described method of handling multiple representations of a resource without modifying the resource URI was using the *Accept* http header of the request. For example client sends the following: GET /users/1 Host: www.mycoolapp.com Accept: text/html This let's us know that the client can handle the html representation of the resource located at /users/1 At the same time, if we were making an API request, we could issue the following: GET /users/1 Host: www.mycoolapp.com Accept: myapp+v1/xml Which would tell our server that client is capable of handling the v1 of our api and expects the response in XML format or json: GET /users/1 Host: www.mycoolapp.com Accept: myapp+v1/json So I am not sure if this needs to be part of the framework, but I sure wanted to share my thoughts on the subject and I'd love to hear your feedback and thoughts. Best, On Mon, Nov 15, 2010 at 1:35 PM, Pablo Godel <[email protected]> wrote: > If there are no topics which I doubt it could happen, at least this week, > these meetings could be also useful to discuss current status and roadmap of > missing or existing features, ie. the form framework, the admin generator. > > Pablo > > > On Mon, Nov 15, 2010 at 8:10 AM, Lukas Kahwe Smith <[email protected]>wrote: > >> >> On 12.11.2010, at 10:42, Lukas Kahwe Smith wrote: >> >> > Hi, >> > >> > Just a reminder to submit topics for next weeks meeting. >> > >> > Once again here are the notes from last week: >> > http://trac.symfony-project.org/wiki/IRCLogs20101111 >> > >> > One thing I ask people submitting stories, try to invest a bit of time >> into the background infos. Make sure that you identify different subtopics >> and proposals with clear identifiers so that they can be referred to during >> the IRC meeting. >> > >> > I will write up some more guidelines and hints as part of the official >> Symfony2 docs in the coming days. >> >> >> i havent written these guidelines yet. but i wanted to make clear that >> nobody should keep an important topic for discussion to themselves because >> they do not have the time or interest to write up a detailed proposal. >> >> i am also saying this because so far there have not been any proposals >> sent for this thursday, which makes me wonder if either i scared people off >> with the above, that people didnt think the meeting is useful, or that >> simply right now there are no issues to discuss. >> >> i do see a few topics of relevance personally though: >> 1) Console dependency injection: >> https://github.com/fabpot/symfony/pull/70 >> 2) Base form templates adjustment: >> https://github.com/fabpot/symfony/pull/100 >> 3) Allow multiple routing requirement with xml loader: >> https://github.com/fabpot/symfony/pull/88 >> 4) Extension helpers: https://github.com/fabpot/symfony/pull/133 >> 5) Security layer and different authentication sources: I think Thibault >> also identified an issue when using different authentication sources, there >> was a pull request but it was lost in yesterday's github outage. >> 6) Flash messages and i18n: >> http://groups.google.com/group/symfony-devs/browse_thread/thread/514d9653cf068725/1c4f2753c553cf4b#1c4f2753c553cf4b >> >> Actually 3) might just need a clarification what was broken with the >> patch, so that a new patch can be written. >> >> Anyway, since I proposed these meetings, it kinda feels wrong if I then >> also dominate the list of topics. >> >> 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]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- *Bulat Shakirzyanov* | Software Alchemist *a: *about.me/avalanche123 *e:* [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
