Timeline for Service Layer to Retrieve Data Specific to Views
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2015 at 21:05 | vote | accept | Chris Klepeis | ||
| Oct 2, 2015 at 14:36 | comment | added | Ewan | I guess the more you optimise to reduce the number of requests the closer you get to returning the viewmodel | |
| Oct 2, 2015 at 14:08 | comment | added | Chris Klepeis | I did something similar in the past... each POCO had a related repository with basic CRUD functions and the ViewModel would be responsible for determining whats pulled and associated the results together. I did this in the past through a data access class library. With this project I definitely need to expose it through services... and would like to limit the amount of round trips to the services layer if possible.... implications may be negligible... not sure yet. | |
| Oct 2, 2015 at 14:04 | history | edited | Ewan | CC BY-SA 3.0 |
added 496 characters in body
|
| Oct 2, 2015 at 13:53 | history | answered | Ewan | CC BY-SA 3.0 |