How do I choose between WCF, REST, POX and RIA services for a new Silverlight application -


A silverlight application can add it to a lot in different ways' server <

  • (or it is still left?)
  • Pox - Plain old XML (e.g., original XML)
  • For each of these, please say what is for this and when you will not use it or not, I have a very large description of "rules of thumb" for selection between them. not I see In.

    (The problem is that when designing your first Silverlight app, you should know that it is time to know all those who do not.)

    My two Euro Euro:

    WCF The service can be seen as a business layer, when your service is "intelligent" like "CalculateDiscountForClient" .

    ADO. Net Data Services (In fact, only a permanent implementation) is appropriate when your application is basically data-centric and the service is only a front-end for the database. That is, all of your service methods are GetCustomers, CreateInvoice, etc.

    RIA Services is a very new technology I have not used yet, but it seems that the application is useful in making applications, including the Silverlight part and service too tightly. Together: You define your service classes and methods in the service project, and they are automatically replicated in the Silverlight project in design time. In addition, you can define both WCF-style "action" methods and ADO.NET data service-style "data" methods. Use Pox if the future of the client part is changed from the client's future to any other technology (for example HTML + AJAX), then use it. Most interoperable options

    Regarding the differences of WPF, only I can think that for data access, whenever possible I will directly use ADOnate Data Connection (properly embedded in Data Access Layer, LINQ From SQL or like) instead of ADO.NET data services, because it is a more flexible way I have to say anyway that I have never developed anything in WPF.


    Comments

    Popular posts from this blog

    asp.net - Javascript/DOM Why is does my form not support submit()? -

    sockets - Delphi: TTcpServer, connection reset when reading -

    javascript - Classic ASP "ExecuteGlobal" statement acting differently on two servers -