Timeline for Exposing domain models over API
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 25, 2013 at 11:51 | vote | accept | James | ||
| Sep 24, 2013 at 16:32 | answer | added | smp7d | timeline score: 3 | |
| Sep 24, 2013 at 14:04 | answer | added | viniciushana | timeline score: 6 | |
| Sep 24, 2013 at 12:35 | comment | added | James | I've edited my question to provide some more clarity, but essentially what I mean is, my User object has some properties such as Password and DateCreated that should not be shown in the JSON representation of the User, but most of the other user data should be available. I'm wondering if DTOs can help me separate the available properties from the unavailable ones. | |
| Sep 24, 2013 at 12:29 | history | edited | James | CC BY-SA 3.0 | clarity |
| Sep 24, 2013 at 11:51 | comment | added | Uooo | "I'm building a simple public API" and "I obviously don't want to publicly expose every property" do not make sense for me, could you please clarify what you mean? | |
| Sep 24, 2013 at 10:47 | history | asked | James | CC BY-SA 3.0 |