Comments on: Why learning HTTP does matter http://blog.codevader.com/2008/11/02/why-learning-http-does-matter/ Thoughts from the nice people at Codevader :) Sat, 19 May 2012 20:21:06 +0000 http://wordpress.org/?v=2.6.2 By: Porque é importante saber como o protocolo HTTP funciona « Alinhavado http://blog.codevader.com/2008/11/02/why-learning-http-does-matter/#comment-710 Porque é importante saber como o protocolo HTTP funciona « Alinhavado Fri, 07 Nov 2008 02:26:10 +0000 http://blog.codevader.com/?p=65#comment-710 [...] Tradução de “Why learning HTTP does matter”, prometo que eu vou traduzir mais posts de lá, é só ter tempo o suficiente, de qualquer forma, [...] [...] Tradução de “Why learning HTTP does matter”, prometo que eu vou traduzir mais posts de lá, é só ter tempo o suficiente, de qualquer forma, [...]

]]> By: Rafael Ponte http://blog.codevader.com/2008/11/02/why-learning-http-does-matter/#comment-706 Rafael Ponte Tue, 04 Nov 2008 03:41:09 +0000 http://blog.codevader.com/?p=65#comment-706 Exactly Maurício, unfortunately JSF doesn't support GET requests by specification yet, well, actually it exists a framework to help it about that, Restfaces. I hope so much that JSF 2.0 brings GET support, at least something seemed with the Restfaces, or better, of course. Thanks and congratulations by post! Exactly Maurício, unfortunately JSF doesn’t support GET requests by specification yet, well, actually it exists a framework to help it about that, Restfaces.

I hope so much that JSF 2.0 brings GET support, at least something seemed with the Restfaces, or better, of course.

Thanks and congratulations by post!

]]> By: Maurício Linhares http://blog.codevader.com/2008/11/02/why-learning-http-does-matter/#comment-701 Maurício Linhares Sun, 02 Nov 2008 19:13:28 +0000 http://blog.codevader.com/?p=65#comment-701 Hi Rafael, Looking at the frameworks that I have used, none of them really worries about it, but Rails was the first one that I've used that cares about HTTP and using the right methods. The RESTful approach that Rails takes in building web applications simplifies a lot of this work and lead you to think about the right methods and the right way to respond to the user. Even when you're using the code generators for Rails controllers they usually redirect the user to the "success" page after a successful post, so Rails tries to put you in the right path, you just have to keep walking on it. On the other side, other frameworks, mostly Java Server Faces and ASP.NET, just forget how the HTTP protocol works and do everything using POSTs (the JSF committee said that GET support is planed for version 2.0, but I coudn't find anything "real" about this). This is a common problem of the "component based" web frameworks, you might find this behaviour in other frameworks in other languages that follow the "component based" approach to web application development, like PHP's PRADO framework. Hi Rafael,

Looking at the frameworks that I have used, none of them really worries about it, but Rails was the first one that I’ve used that cares about HTTP and using the right methods. The RESTful approach that Rails takes in building web applications simplifies a lot of this work and lead you to think about the right methods and the right way to respond to the user.

Even when you’re using the code generators for Rails controllers they usually redirect the user to the “success” page after a successful post, so Rails tries to put you in the right path, you just have to keep walking on it.

On the other side, other frameworks, mostly Java Server Faces and ASP.NET, just forget how the HTTP protocol works and do everything using POSTs (the JSF committee said that GET support is planed for version 2.0, but I coudn’t find anything “real” about this). This is a common problem of the “component based” web frameworks, you might find this behaviour in other frameworks in other languages that follow the “component based” approach to web application development, like PHP’s PRADO framework.

]]> By: Rafael Ponte http://blog.codevader.com/2008/11/02/why-learning-http-does-matter/#comment-700 Rafael Ponte Sun, 02 Nov 2008 04:10:13 +0000 http://blog.codevader.com/?p=65#comment-700 Excellent post Mauricio, I think it's necessary to understand about base concepts of any frameworks and/or technologies that we use daily to develop software, and http protocol is not different, mainly when we're developing web applications. You commented that after successful POST we should redirect the user to a new page and not just render the page for him, I really agree you, but the most MVC frameworks don't worry with this. Then, we're obligated to implement the Post-Redirect-Get Pattern [http://en.wikipedia.org/wiki/Post/Redirect/Get]. Do you know some framework that worry about it? Excellent post Mauricio,

I think it’s necessary to understand about base concepts of any frameworks and/or technologies that we use daily to develop software, and http protocol is not different, mainly when we’re developing web applications.

You commented that after successful POST we should redirect the user to a new page and not just render the page for him, I really agree you, but the most MVC frameworks don’t worry with this. Then, we’re obligated to implement the Post-Redirect-Get Pattern [http://en.wikipedia.org/wiki/Post/Redirect/Get].

Do you know some framework that worry about it?

]]>