Timeline for C# class architecture for REST services
Current License: CC BY-SA 2.5
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 3, 2011 at 15:58 | comment | added | quentin-starin | 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. | |
| Feb 3, 2011 at 14:51 | comment | added | user15370 | 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. | |
| Feb 2, 2011 at 20:09 | history | answered | quentin-starin | CC BY-SA 2.5 |