Rest is a well known concept in the world of HTTP. However, it didn't fully make it through to Web Services until very recently. RESTful Web Services became popular with many benefits of REST against SOAP, which would drive SOA towards its ultimate potential.
However, it is a well known fact that REST and SOAP do things differently. Thus, the requirement of new implementations are needed. The WSDL 2.0 HTTP Extensions do provide some convenient implementation of REST for existing SOAP engines, but, RESTful Web Services demands more.
Axis2/C addresses these demands well. Now it has support for HTTP Headers (Standard and Custom), the entire range of valid HTTP Status Codes, and also has the capability to handle several content types, demanded by RESTful implementations.
At present, Axis2/C still lacks the support for much needed x-www-form-urlencoded, which I hope to add in the future. I hope that the experience of Axis2/C REST implementation is as RESTful as one would expect.
However, it is a well known fact that REST and SOAP do things differently. Thus, the requirement of new implementations are needed. The WSDL 2.0 HTTP Extensions do provide some convenient implementation of REST for existing SOAP engines, but, RESTful Web Services demands more.
Axis2/C addresses these demands well. Now it has support for HTTP Headers (Standard and Custom), the entire range of valid HTTP Status Codes, and also has the capability to handle several content types, demanded by RESTful implementations.
At present, Axis2/C still lacks the support for much needed x-www-form-urlencoded, which I hope to add in the future. I hope that the experience of Axis2/C REST implementation is as RESTful as one would expect.
2 comments:
Very nice post...Simply Superb!!!
Thanks for the comment.
Post a Comment