Timeline for What is the best design decision approach?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 27, 2014 at 10:53 | comment | added | Konamiman | That's it. In the end the question when doing a design decision should always be, "What will be easier to read?" (or "What would another person find easier to understans?" if you want) | |
| Nov 23, 2011 at 6:46 | history | migrated | from stackoverflow.com (revisions) | ||
| Nov 22, 2011 at 19:29 | vote | accept | CommunityBot | ||
| Nov 22, 2011 at 16:49 | comment | added | Mark J Miller | If that's the case, then I would wrap the 3rd party library in a utility class or interface and provide the common functionality to the classes that way. This allows you to change out 3rd party libraries and enforce the boundary between the external dependency and your code. | |
| Nov 22, 2011 at 16:30 | comment | added | palm snow | Each of these two classes interface with a third party library to fulfill a unique functionality. In some cases they use third party library in same way; in other each of it has own way of calling and processing response from same third party library. | |
| Nov 22, 2011 at 16:22 | history | answered | Justin Niessner | CC BY-SA 3.0 |