Thanks all.
On Sat, Aug 20, 2011 at 8:35 PM, wrote:
>
> RESTful services are almost exclusively used over the HTTP protocol. I
> suppose you *could* use a different protocol if you were determined to do so
> but, speaking for myself, if you need another protocol I'd recommend using
> SOAP.
>
> T
RESTful services are almost exclusively used over the HTTP protocol. I
suppose you *could* use a different protocol if you were determined to
do so but, speaking for myself, if you need another protocol I'd
recommend using SOAP.
The server where the REST service is deployed must be a web
Thank. One last question:
In what way RESTful services are interoperable? They are bound to HTTP
protocol and therefore it effectively means we need HTTP capable clients and
servers to handle RESTful messages. Now REST messages goes as HTTP request
and response body (like XML encapsulated into req
You can do the exact same things with either approach because, at the
end of the day, RAX-RS is built on top of the servlet API so it stands
to reason that you can do the same things in either. I can think of a
couple big distinctions between them off the top of my head.
1) JAX-RS is a stan
Hi
On Thu, Aug 18, 2011 at 7:18 AM, Raj Floyd wrote:
> Hi
>
> REST style architecture, being based on HTTP specification, has common
> conventions like GET, POST typically also used by Servlets. Any idea why one
> would prefer RESTful Web service and not plain Servlet based framework. Its
> Web a
Hi
REST style architecture, being based on HTTP specification, has common
conventions like GET, POST typically also used by Servlets. Any idea why one
would prefer RESTful Web service and not plain Servlet based framework. Its
Web and HTTP in the end. I know this question may not be directly relat
