Last post Jul 10, 2017 06:11 AM by Edward Z
Jul 07, 2017 10:39 PM|tapan2017|LINK
when i try to know what is rest then i found this explanation :
REST is an architectural style, while SOAP is a protocol. REST is not a standard in itself, but RESTful implementations make use of standards, such as HTTP, URI, JSON, and XML.
it is not very clear to me. how make a understand what is rest to layman?
when action is mapped and called by http verb then that kind of service will be called REST?
why web api is called rest ?
explain in such a way as a result i can explain it to layman.
Jul 08, 2017 05:51 AM|bruce (sqlwork.com)|LINK
follow this thread:
but basically SOAP was designed because COM+ became too complex. Now SOAP has gotten too complex (try to understand a typical wsdl file without tooling), so REST has replaced it. Originally REST was simple xml/in and xml/out, just almost REST services are
now JSON based instead of xml.
instead of a wsdl file, most REST services now use swagger if they want the API discoverable.
Jul 08, 2017 07:38 PM|tapan2017|LINK
you did not mention why web api is called rest?
Jul 10, 2017 06:11 AM|Edward Z|LINK
Web service APIs that adhere to the REST architectural constraints are called RESTful APIs. HTTP-based RESTful APIs are defined with the following aspects: base URL, an internet media type and standard HTTP methods.
Web Api follows REST architectural constraints.
You could refer below link for more information.
# Applied to Web services