Is the WebGetAttribute just syntactic sugar for the WebInvokeAttribute with Method = “GET”?
Or is there an underlying difference?
Is the WebGetAttribute just syntactic sugar for the WebInvokeAttribute with Method = GET? Or
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is the WebGetAttribute just syntactic sugar for the WebInvokeAttribute with Method = “GET”?
Or is there an underlying difference?
Your immediate observation that WebGet and WebInvoke are very similar is not all too far from the truth. WebGet, as you’ve already stated, applies to the HTTP GET verb while WebInvoke can be used to apply to all the other verbs (PUT, POST, DELETE, etc).
Many of the parameters in WebInvoke mirror those in WebGet. BodyStyle, RequestFormat, ResponseFormat, and UriTemplate are all present for both WebGet and WebInvoke. The one differentiator is the presence of the “Method” parameter for WebInvoke. The Method parameter specifies the HTTP verb that corresponds to the operation, with POST being the default value.
I haven’t had the chance to use Reflector to look under the hood for WebGet and WebInvoke but I suspect that they are very much alike even though they only seem to share System.Attribute as a common lineage.