title: Design/Implementation advice on XML Parsing with multiple connections/feeds/views
body: <p>Starting my first iOS project and wanted to advice on how to structure the application.
  The app pulls a XML feed, parses it out and displays a list representing the items in the XML feed. When clicking on a item in the list the app will pull a new XML feed using one of the attributes from the previously pulled XML feed. This happens several layers of pull, parse, display and on user selection do the same thing over again. Now most of the XML element structure is something like this: </p>
  
  <p>(These are simple examples just to demonstrate what's going on)</p>
  
  <ul>
  <li><a href="http://site.com/get/items/">http://site.com/get/items/</a></li>
  </ul>
  
  <p>returns (Display info on new view):</p>
  
  <pre><code>&lt;items&gt;
      &lt;item id="123" name="item 1" /&gt;
      &lt;item id="124" name="item 2" /&gt;
      &lt;item id="125" name="item 3" /&gt;
  &lt;/itmes&gt;
  </code></pre>
  
  <ul>
  <li><a href="http://site.com/get/description/123">http://site.com/get/description/123</a> (Example user has selected item 1, make call to get description)</li>
  </ul>
  
  <p>returns:</p>
  
  <pre><code>&lt;itemDescription&gt;
      &lt;description itemId="123" name="desc 1" description="blah 1" /&gt;
  &lt;/itemDescription&gt;
  </code></pre>
  
  <p>Wanted to know:</p>
  
  <ul>
  <li>Should I have a connection class/object or a new connection in each view?</li>
  <li>Should I have a parser class/object or parse the XML feed in each view?</li>
  <li>I'm also looking to store some of the data returned so I don't need to call the XML feed again if the user navigates back to the main items list, but I would need to parse the itemsDescription XML feed every time. </li>
  </ul>
  
  <p>I've looked at several tutorials on parsing XML and I get the gist of how to do this, wanting to focus more of the design and reusability instead of duplicating the code over in each new view. Or am I way off on how this works </p>