title: Information from local DB and external source in one view
body: <p><strong>Situation:</strong><br>
  The simplified situation is this: consider a blog that is build as an MVC project. The YII blog-example is fine for this, but the question is not framework specific: It is nothing special; you have a table with posts and a page build from:</p>
  
  <ul>
  <li>a model (YII will give you a basic active-record setup)</li>
  <li>a controller that for instance builds the index (list of all posts)</li>
  <li>a view (or some views) that build the actual HTML in the end.</li>
  </ul>
  
  <p>Now I have a working blog, but I also have an external source of information that I want to introduce to this same page: for example an RSS feed. </p>
  
  <p>How do I add this new datasource?</p>
  
  <p><strong>Possible sollutions</strong><br>
  To clarify what I am struggling with, here are some things I am considering</p>
  
  <ul>
  <li>Make a new model that gets its information from both sources
  <ul>
  <li>Feels like the way of least resistance/work</li>
  <li>It would need to sort the blogposts and RSS items by date</li>
  <li>It might need to give some sort of flag about what kind of item it is (An RSS item might not have an author, but it does have a source).</li>
  <li>The fact that above flag feels neccessairy makes me believe these should be 2 models.</li>
  </ul></li>
  <li>Make a new model for the RSS and make a controller that combines the two sources and feeds it to a view that can handle both types of post</li>
  <li>Something more complicated (maybe more framework specific), but the current view of a post is just one view for one post, and it gets repeated. Instead of one view that handles both types you might want not only a model, but also a view for your RSS, and a controller(?) that does all the mixing and matching?</li>
  </ul>
  
  <p><strong>Framework notes:</strong><br>
  I'm using YII, but it's not really about YII. Ofcourse if something complicated is to be done I will have to implement it in YII, but it's about the design and the MVC pattern, not about where to put the <code>;</code> ;D</p>