Brandon Savage's latest post in his "Peer Review" series has been added to his blog today. This time he focuses on the requests and responses - modifying the sample code to make it more testable on how things are quested and the responses they give back.

There is one last area that I want to address, and this has everything to do with object-oriented principles and code reusability. For those who are familiar with OO programming, they realize that the use of classes does not make something object oriented by nature. In this final part of the series, we'll move one step closer to being object-oriented, by introducing the concepts of request and response objects.

He changes up the Twitter object to take in a HTTPRequest object (instead of creating one by itself) and to use exceptions and a "Twitter response object" to encapsulate any responses from the service making it much easier to work with and understand than just a true/false return.