Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
By design is it a good idea to expose the domain model entities as data contracts? May be the question is too basic. In my case I saw that I can wrap the entites in request and reponse objects and use them as data contracts. I just wanted to know whether its good idea to do the same?
Assuming that your entities are being loaded from a database and if you are looking for loose coupling and interoperability you may not want to send the entities to your client.
However if the client is well known (internal application), and you want rich functionality offered by these entities (validation etc..) you can send entities directly.