I had a programming assessment recently. It was on a Rails app I had build and my assessor asked me a question. “You enter the URL in you browser and hit enter… then what happens?” At that question I was a bit tripped up. “What does this question even mean?”, I thought. I mean, I know that a http GET request gets sent to the server and a the server responds. But let’s break into that a little. ‘an http GET request gets sent’. How? ‘the server responds’ How? The same thing happened when my assessor came to this question, “The router processes the get request, then what happens?” Well, I understand the MVC architecture but, how and where is the data flowing to and from. Rails provides a bit of magic (resources) and I just used those to wire up the app. But what is resources doing?
In this blog post:
I would like to describe some common mechanisms of web development and how they relate.
Who is it for:
This post if for those who have heard the “handshake” explanation for http requests and want a bit more. It is also for those that have heard the “cafe” description of MVC design pattern. In other words, I don’t care for euphemism. This is how I best understand things. It’s for newish Web Developers who want an overview of the domain they will be building in. I will be writing this from a Rails framework perspective.