My feedback

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Zoran commented  · 

    Ok. Thanks.

    An error occurred while saving the comment
    Zoran commented  · 

    But it is fine. This isn't a deal breaker for me. It was just convenient to be able to POST list data via the Form and I thought it would also be useful to be able to do that with service stack especially for people who decide to use it as a replacement for ASP.NET MVC as well as WCF/WebAPI.

    An error occurred while saving the comment
    Zoran commented  · 

    I suppose that is a matter of opinion. Here is my thought process on this. I have a page where I need to ask the user a few (dynamic) questions. So I created a Step1Questions DTO that contains a Questions List property (List<Question> Questions). So, the user can use a GET request for Step1Questions and I populate a Step1QuestionsResponse DTO with the questions and then use the SS Razor view engine to render out the questions to the user as a html form. Now, I would like to be able to POST that form to the server and have those questions deserialized into the Step1Questions.Questions list. Doesn't it make logical sense that I should be able to POST this data back to the server using the Form mechanism? I know I can pull it off by getting javascript involved, but why do that, as it requires more code initially and to maintain for the lifetime of the app. One of the main reasons I chose ServiceStack as a replacement is because it just seems to work, almost "magically", and I don't see that as a bad thing. But that's just my opinion.

    Zoran shared this idea  · 

Feedback and Knowledge Base