Dto/TransactionScripts and Odata Services -
with odata service, can query clientside without using dto. need dto layer if use odata svc? cons , pros if don't use dto. in our old system querying mechanism there many query service-methods returns dto collection. odata services confuses mind... seems like; responsibility of server moves client. same confusion goes on, transaction scripts. i'm curios thoughts.
when on server side - thing matters odata either edm model or poco models. when genrate edmx file can considered business object or model layer , pump in namespaces. in way there no business logic applying in there.
but on client side can centralize odata method invocation. since support callbacks can have view model call repository , pass call back. in way dont bloat view model extensive odata query invocation. sort of repositroy pattern talking about.
hope gives direction.
regards :)
Comments
Post a Comment