Comments on: MVC and web apps: oil and water http://www.sitepoint.com/blogs/2005/12/22/mvc-and-web-apps-oil-and-water/ News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com. Mon, 23 Nov 2009 01:39:24 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: faffy fuck http://www.sitepoint.com/blogs/2005/12/22/mvc-and-web-apps-oil-and-water/comment-page-1/#comment-894935 faffy fuck Mon, 16 Mar 2009 14:01:48 +0000 http://www.sitepoint.com/blogs/?p=1360#comment-894935 <em>"This might just mean finding smarter ways to write view centric code, emphasizing DRY while avoiding spaghetti - consider the “article.php” in this URL."</em> Are you by any chance talking about a recipe for soup? “This might just mean finding smarter ways to write view centric code, emphasizing DRY while avoiding spaghetti – consider the “article.php” in this URL.”

Are you by any chance talking about a recipe for soup?

]]> By: James Watt http://www.sitepoint.com/blogs/2005/12/22/mvc-and-web-apps-oil-and-water/comment-page-1/#comment-609156 James Watt Tue, 22 Jan 2008 04:55:22 +0000 http://www.sitepoint.com/blogs/?p=1360#comment-609156 I completely agree with this article. Nice read. I have actually thought this for some time now, but never wanted to take the time to argue the point. I completely agree with this article. Nice read. I have actually thought this for some time now, but never wanted to take the time to argue the point.

]]> By: Justin http://www.sitepoint.com/blogs/2005/12/22/mvc-and-web-apps-oil-and-water/comment-page-1/#comment-441828 Justin Thu, 08 Nov 2007 00:38:43 +0000 http://www.sitepoint.com/blogs/?p=1360#comment-441828 I'd like to know what you think about a JavaScript MVC framework like Junction (http://jupiterit.com/junction.html). It allows a more natural development because you have access to data (exposed through services) and the DOM at the same time. I’d like to know what you think about a JavaScript MVC framework like Junction (http://jupiterit.com/junction.html).

It allows a more natural development because you have access to data (exposed through services) and the DOM at the same time.

]]> By: martynas http://www.sitepoint.com/blogs/2005/12/22/mvc-and-web-apps-oil-and-water/comment-page-1/#comment-363764 martynas Mon, 03 Sep 2007 00:45:40 +0000 http://www.sitepoint.com/blogs/?p=1360#comment-363764 This article was one of the inspirations :) And so we developed our own RESTful PHP framework, based on Resources that have URIs and implement HTTP methods. http://www.xml.lt/Resources/Framework This article was one of the inspirations :) And so we developed our own RESTful PHP framework, based on Resources that have URIs and implement HTTP methods.
http://www.xml.lt/Resources/Framework

]]> By: cesium62 http://www.sitepoint.com/blogs/2005/12/22/mvc-and-web-apps-oil-and-water/comment-page-1/#comment-31789 cesium62 Wed, 21 Jun 2006 20:38:04 +0000 http://www.sitepoint.com/blogs/?p=1360#comment-31789 MVC is used because you want to be able to use the same functionality through multiple interfaces. We used MVC in 1997 without knowing what it was called because we wanted to interface our database not only to users via HTML, but to other web sites via Soap, to Sabre via EDIFACT, and to Wizcom via some other random protocol. When you have N implementations of your controller and view, and one implementation of the the model, you use MVC. And lo and behold, this is pretty much what a 3 tier architecture provides. MVC is used because you want to be able to use the same functionality through multiple interfaces. We used MVC in 1997 without knowing what it was called because we wanted to interface our database not only to users via HTML, but to other web sites via Soap, to Sabre via EDIFACT, and to Wizcom via some other random protocol. When you have N implementations of your controller and view, and one implementation of the the model, you use MVC. And lo and behold, this is pretty much what a 3 tier architecture provides.

]]> By: M.Uma Sankar http://www.sitepoint.com/blogs/2005/12/22/mvc-and-web-apps-oil-and-water/comment-page-1/#comment-17011 M.Uma Sankar Tue, 04 Apr 2006 14:31:30 +0000 http://www.sitepoint.com/blogs/?p=1360#comment-17011 Differences between 3tier architecture and MVC Differences between 3tier architecture and MVC

]]> By: Steve’s Log » Blog Archive » MVC and web apps: oil and water http://www.sitepoint.com/blogs/2005/12/22/mvc-and-web-apps-oil-and-water/comment-page-1/#comment-15811 Steve’s Log » Blog Archive » MVC and web apps: oil and water Fri, 17 Mar 2006 20:43:34 +0000 http://www.sitepoint.com/blogs/?p=1360#comment-15811 [...] This entry was posted on Thursday, December 22nd, 2005 at 7:34 am, contains 2,471 words, and is filed under PHP. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site. The views and opinions in this blog post are those of its author. [...] [...] This entry was posted on Thursday, December 22nd, 2005 at 7:34 am, contains 2,471 words, and is filed under PHP. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site. The views and opinions in this blog post are those of its author. [...]

]]> By: Jumping on the MVC Bandwagon at d3 eMinistry blog http://www.sitepoint.com/blogs/2005/12/22/mvc-and-web-apps-oil-and-water/comment-page-1/#comment-15238 Jumping on the MVC Bandwagon at d3 eMinistry blog Tue, 07 Mar 2006 00:39:10 +0000 http://www.sitepoint.com/blogs/?p=1360#comment-15238 [...] go back to step 1 Not rocket science. With AJAX, things are different. Now, when I can specify what part of the page is updated and when it’s updated. Add to this the ability to have updates to the page done completely asynchronously and you have a programmer’s dream come true…or worst nightmare. I’ve been using Taconite. It’s a Java Script library that processes XMLHttpRequest and easily allows you use the returned data for any HTML element on your page. If I’m displaying data from a table in a form and the user deletes a row from that table, after I process the action for the database, all I have to do is have Taconite delete that table row. Anything with an ID attribute can be added to, removed, replaced, etc. all without InnerHTML. It’s funny, but I think the Web 2.0 thing has made backends much more complex. Complex gone wrong is complicated and that’s where I was at that night last week. I needed a new way to organize my backend. I’ve been actually thinking about this for some time. I’ve looked into the many PHP frameworks out there and they just seem so…cumbersome. I didn’t want to have to change the way I think to use one of these things. I liked the idea, I didn’t like the implementations I was seeing. Then I came across an excellent post at fiftyfoureleven.com titled PHP and MVC without the OOP. Maybe it’s the Military in me, but all those acronyms caught my eye. I don’t have a specific problem with OOP. That’s what I was taught in high school and my first couple of years of college. It’s a nice way of doing things. I know there’s a passionate debate on both sides of the fence: OOP and procedural. It’s like arguing religion or worse, politics. I think it boils down to personal preference and for some reason I just perfer procedural. This doesn’t mean that I don’t get OOP, I’ve never had a problem understanding objects. I like how the MVC way of doing things organizes your code by what it does (see Harry Fuecks’ article): [...] [...] go back to step 1 Not rocket science. With AJAX, things are different. Now, when I can specify what part of the page is updated and when it’s updated. Add to this the ability to have updates to the page done completely asynchronously and you have a programmer’s dream come true…or worst nightmare. I’ve been using Taconite. It’s a Java Script library that processes XMLHttpRequest and easily allows you use the returned data for any HTML element on your page. If I’m displaying data from a table in a form and the user deletes a row from that table, after I process the action for the database, all I have to do is have Taconite delete that table row. Anything with an ID attribute can be added to, removed, replaced, etc. all without InnerHTML. It’s funny, but I think the Web 2.0 thing has made backends much more complex. Complex gone wrong is complicated and that’s where I was at that night last week. I needed a new way to organize my backend. I’ve been actually thinking about this for some time. I’ve looked into the many PHP frameworks out there and they just seem so…cumbersome. I didn’t want to have to change the way I think to use one of these things. I liked the idea, I didn’t like the implementations I was seeing. Then I came across an excellent post at fiftyfoureleven.com titled PHP and MVC without the OOP. Maybe it’s the Military in me, but all those acronyms caught my eye. I don’t have a specific problem with OOP. That’s what I was taught in high school and my first couple of years of college. It’s a nice way of doing things. I know there’s a passionate debate on both sides of the fence: OOP and procedural. It’s like arguing religion or worse, politics. I think it boils down to personal preference and for some reason I just perfer procedural. This doesn’t mean that I don’t get OOP, I’ve never had a problem understanding objects. I like how the MVC way of doing things organizes your code by what it does (see Harry Fuecks’ article): [...]

]]> By: SitePoint Blogs » PHP Security: Dumb Users or Dumb APIs? http://www.sitepoint.com/blogs/2005/12/22/mvc-and-web-apps-oil-and-water/comment-page-1/#comment-13075 SitePoint Blogs » PHP Security: Dumb Users or Dumb APIs? Tue, 24 Jan 2006 15:36:42 +0000 http://www.sitepoint.com/blogs/?p=1360#comment-13075 [...] And it’s likely we’ll have to make future bids based on this platform (release early, release often!), and encourage others to do the same. For the sake of the newbies, I hope “Extreme Simplicity” and MVC are able to fit into the same sentence. [...] [...] And it’s likely we’ll have to make future bids based on this platform (release early, release often!), and encourage others to do the same. For the sake of the newbies, I hope “Extreme Simplicity” and MVC are able to fit into the same sentence. [...]

]]> By: Vysnu » MVC and web apps: oil and water http://www.sitepoint.com/blogs/2005/12/22/mvc-and-web-apps-oil-and-water/comment-page-1/#comment-12840 Vysnu » MVC and web apps: oil and water Tue, 17 Jan 2006 22:45:54 +0000 http://www.sitepoint.com/blogs/?p=1360#comment-12840 [...] and water. A pretty detailed examination of the MVC model, a good, long, but rather confusing read. # Development |Web [...] [...] and water. A pretty detailed examination of the MVC model, a good, long, but rather confusing read. # Development |Web [...]

]]>