ServiceStack CRUD 服务路由文档

Question

我找不到说明如何使用多种方法在服务堆栈中实现服务的文档(清晰或其他)。所有示例都显示了仅具有一种方法的服务类。我无法想象如果你有一个服务有 4 个以上的方法，你真的需要制作 4 个以上的服务类，4 个以上的请求 DTO 和 4 个以上的响应 DTO。 ( As shown here )

示例:

具有 4 种搜索方法的服务(method(Identifer1)、method2(identifer2)、method3(identifer3))

基于请求 DTO(Service Stack Wiki 和 Creating your First Web Service)的记录结构，请求 DTO 的类属性控制到服务类的路由，(如果我理解正确，但我再次寻找文档或示例)

关于路由的文档有点模糊，因为大多数示例不遵循“Your First Web Service Explained”中概述的请求/响应 DTo 定义的命名约定

我也读过这个SO Post ，但在遵循建议后，我仍然有同样的问题。

Answer 1

I cant imagine if you have a service with 4+ methods, that your really need to make 4+ service classes, 4+ Request DTO's and 4+ response DTO's.

不，您需要 1 个具有 4 个方法的服务类 - 每个方法当然接受一个请求 Dto 并返回一个 Response Dto。显然，对于某些方法，您可能不需要响应 Dto

例如，具有 5 个方法的典型服务可能如下所示:

public class ProductsService: Service
{
    [Route("/products")]
    public class GetProductsRequest: IReturn<List<ProductResponse>> {}

    public class ProductResponse
    {
        public int Id { get; set; }
        public string Name { get; set; }
    }

    public object Get(GetProductsRequest request)
    {
        IEnumerable<ProductResponse> response = ...
        return response;
    }

    [Route("/products/{id}")]
    public class GetProductRequest: IReturn<ProductResponse> 
    {
        public int Id { get; set; }
    }

    public object Get(GetProductRequest request)
    {
        ProductResponse response = ...
        return response;
    }

    [Route("/products")]
    public class CreateProductRequest 
    {
        public string Name { get; set; }
    }

    public object Put(CreateProductRequest request)
    {
        ... create the product here
        return new HttpResult { StatusCode = HttpStatusCode.Created };
    }

    [Route("/products/{id}")]
    public class UpdateProductRequest
    {
        public int Id { get; set; }
        public string Name { get; set; }
    }

    public object Patch(UpdateProductRequest request)
    {
        ... update the product here
        return new HttpResult { StatusCode = HttpStatusCode.Accepted };
    }

    [Route("/products/{id}")]
    public class DeleteProductRequest
    {
        public int Id { get; set; }
    }

    public object Delete(DeleteProductRequest request)
    {
        ... delete the product here
        return new HttpResult { StatusCode = HttpStatusCode.Accepted };
    }
}

我已将请求和响应 DTO 作为服务的嵌套类放置，但将它们放在单独的文件中会使其更具可读性:

public class ProductsService: Service
{
    public object Get(GetProductsRequest request)
    {
        IEnumerable<ProductResponse> response = ...
        return response;
    }

    public object Get(GetProductRequest request)
    {
        ProductResponse response = ...
        return response;
    }

    public object Put(CreateProductRequest request)
    {
        ... create the product here
        return new HttpResult { StatusCode = HttpStatusCode.Created };
    }

    public object Patch(UpdateProductRequest request)
    {
        ... update the product here
        return new HttpResult { StatusCode = HttpStatusCode.Accepted };
    }

    public object Delete(DeleteProductRequest request)
    {
        ... delete the product here
        return new HttpResult { StatusCode = HttpStatusCode.Accepted };
    }
}