Thanks for your comment. Below is the answer to your questions.

> But what I would like to know, how are you dealing with Data Validation on the client side and server side?

Our data source controls expose numerous events that you can use to perform data vaildation before the data request is sent to server.

On the server side, you can use Query Interceptor on the Astoria’s end point to perform data validation.

> How would a developer set the criteria that could take place on the server side or client side?

Most custom codes can be placed in event handlers, such as Selecting, Selected, Updating, Updated, and so on.

> Or have you thought about having a Business Object system on the server side which uses Astoria in the background…

In fact, Astoria works in concert with ADO.NET Entity Framework. So, you don’t need to use your own business object. However, you can still use your custom business object if you prefer, by simply creating a new data service which is then passed to the Astoria service to be consumed.

We think that Astoria has reached a quite mature point so far, although there are some areas related to query customization that we expect them to improve in their next version.

Let me know if you have other questions. Have a nice day Ben!

Regards,
Jimmy.

Or have you thought about having a Business Object system on the server side which uses Astoria in the background for it’s data pluming and developer will only have to deal with BO for setting Validation and rules and this server BO will work with your client side DataSource and Astoria is used in the middle, as a transparent media?

I think Datasource is greatm but it only addresses half of the problem. What do you think?
Thanks!