title: What was the design decision behind ItemPendingError in Flex?
body: <p>Flex has the notion of lazily loading data. It has a class named ItemPendingError which allows developers to handle it when an attempt is made to access data that is not yet available aka "pending".</p>
  
  <p>However, looking at the <a href="http://livedocs.adobe.com/flex/201/html/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Book_Parts&amp;file=about_dataproviders_057_18.html" rel="nofollow noreferrer">documentation</a> it's clear you have to add try/catch blocks around your code wherever you have code that <strong>might</strong> cause an IPE (ItemPendingError) to occur.</p>
  
  <p>I'm curious if anyone knows why it works this way. I'm not sure what the best solution might be, but having to willy-nilly add in try/catch blocks to catch the error and then register a Responder with it feels bad and not very clean. And the fact that you sort of have to exercise your application to make sure you've caught all the possible places where the error might occur is also lame.</p>
  
  <p>Is there some other way or better approach that I haven't seen/heard of?</p>