I’m fine with REST as a transport mechanism though the resource overload constraint (Swagger) is the sort of thing that might make me dump it.
If I want to overload get with a custom search end point, I should be able to do that without someone’s idea of a perfect resource definition telling me I’m wrong.
This is the sort of thing that made me remove WCF from my resume.
Simple and flexible. This should be any standards mantra.
If I want to overload get with a custom search end point, I should be able to do that without someone’s idea of a perfect resource definition telling me I’m wrong.
This is the sort of thing that made me remove WCF from my resume.
Simple and flexible. This should be any standards mantra.