title: Advantages of IoC and DI in web applications
body: <p>I am studying dependency injection and inversion of control from a manning book, as far as i have understood from the examples, IoC can be applied at application initialisation time.<br>
  When the application starts it reads the xml spring config file and initialises the beans with their dependencies.
  I understand the advantages of this, mainly the testability of completely loose classes is a great advantage.
  What i would like to understand is how to apply IoC and DI on a mvc-based web application, i have built a simple web application in SpringMVC (i normally develop using Stripes), but i cant see how i can take advantage of IoC and DI in a web application flow, where the user navigates through the site, inserts comments, submit forms, upload files for the backend to read them and return some results, fetches data from the DB. <br>All those actions are of course performed after the application is initialised (in the web server), and where IoC has already been applied.
  So i am trying to understand if it is really worth to learn it.
  Any advise/hint/comment/link is appreciated</p>