Home/ Questions/Q 9091385
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-16T22:35:50+00:00

I had some good results with implementing Rest Web Services with ServiceStack Framework, but

  • 0

I had some good results with implementing Rest Web Services with ServiceStack Framework, but I noticed somethings in samples I would like some more information.

  1. I have currently created a Service based on IService interface. What is the differences with using IRestServiceBase? When should I use either one or the other (my web service has routes so it’s REST already right)?

  2. What is the difference between these 2 syntaxes?

    MyEvent : RestServiceBase <Event>
public override object OnGet(...)

    and 

    MyEvent : IService
public object Get(...)

    The one I use with my IService is the second version, is version one being more ‘REST’ than the other? I tested both and did same results.

  3. I have not used attributes [DataMember] or [DataContract] the way it’s done on WCF, in which situation do I have to use this? (to speak the truth I can really pass on adding this useless information).

  4. In Movie sample, what are Interfaces : IRestGetService? What is their purpose when my class already has IService?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The newer style api uses the Service base class. Your service will act just like it did when using RestServiceBase but the new api has a bunch of added benefits which are described in the documentation.

    Use the [DataMember] and [DataContract] attributes when supporting SOAP endpoints.

    IRestGetService is marked obsolete and you should move to the new style api. In the new api, interfaces such as IGet and IPost can be used to enforce the correct method signatures but are not required.

    • 0