Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Thanks for the suggestion. But I don't see how using RestSharp is a solution. I already have a REST interface built that my SearchClient, AnalysisClient, etc... subclasses. I want the app developer to only instantiate an object that maps to the set of REST services exposed by a particular project. Perhaps ProjectClient should subclass the REST interface. Commented Feb 3, 2011 at 14:51
  • Perhaps I misunderstood your question. I thought you were looking for how to design classes that consumed a web api. With that assumption, what I was meaning was to use a library, which will drive the design of the classes. For instance, RestSharp would generate them with T4 templates. But it seems like I maybe missed what you were really asking. Commented Feb 3, 2011 at 15:58