This week we discuss the different options that are available for passing data between a client and a service, as well as common pitfalls around trying to use the same objects for both presentation to the user and persistence to the database.
Hello there,
We are developing an application in .NET Smart Client application which connects to a WCF service and then to the data access layer. The issue we have here is on the type of data which can be passed between the client side and web service.
1. Can it be a dataset (No!), custom entity or XML or anything else ?
Which is the best one ?
2. Of course , a dataset can't be used coz it can't be used in non-.NET environment?
3. If we go for custom-entity or XML how do we ensure the changes happen to the data during client-side actions ? For example, binding the XML or custom entity to a data grid can be done. But if user makes any changes to the same, how do we identify ?
4. If we use custom entities / XML, the same can not be passed to the Data Access Application Block which invokes the data objects.
Note : All the above are based on assumption without using a translator in between any of the layers.
Please provide a better solution if you have come across any.
