Timeline for Where should I use abstract classes vs interfaces for a REST API client?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2017 at 23:32 | comment | added | Frank Hileman | @William-Rem Forgot to mention, "common code" may be the caller; the code invoking properties or methods on the request class or interface. | |
| Mar 16, 2017 at 19:07 | comment | added | Frank Hileman | "Treated equivalently" should mean there is some code in common between the request objects. To be implemented as a class, a request should have either common code or common data across all requests. | |
| Mar 13, 2017 at 23:02 | comment | added | William | I agree that one request on its own doesn't seem like it should require an interface or inheritance. I'm trying to think of the right way to be able to have a variety of requests that could all be treated equivalently: CreateThing, ReadThing, UpdateThing, DeleteThing, UpdateSomeOtherThing, PerformRandomServiceAction, and etc. | |
| Mar 13, 2017 at 22:57 | vote | accept | William | ||
| Mar 6, 2017 at 17:25 | history | answered | Frank Hileman | CC BY-SA 3.0 |