The term REST buzzing for quite some time through the Internet. But what exactly REST is and how to implement REST using Java?
This question has been in the JAX session "Java API for RESTful Web Services" Stefan Tilkov believed Innoq and explained to me very naturally. Below I would like to briefly summarize the most important thing for me this session and hope that the entire slides vn Stefan Tilkov can be downloaded from the JAX website soon.
But back to REST.
If you look around the internet a bit to REST, REST, there are many comparisons with other techniques, such as REST vs. SOA, REST vs.. SOAP and REST vs. WS-* (short for the rather wide range of standards in the web environment).
According to Stefan Tilkov REST is comparable to the best of web services, but rather about his experiences, a different approach to high-level SOA to achieve goals.
Originally, the term REST (Re presentational S tate T ransfer) from a dissertation by Roy Fielding (see wikipedia ) is used in today's parlance, but rather in the sense of the whole "RESTful" use the Hypertext Transfer Protocol (HTTP).
After Tilkovs statements, REST can be reduced to five basic points:
- all things have an ID, technically implemented through the Internet in unique URI
- Things are interconnected
- The use of standard methods (uniform interface), the technical methods of HTTP
GET - for obtaining optional cached information
PUT - create or modify a known ID
POST - Create or attach a sub-resource (sub-resource)
DELETE - (logical) deletion
HEAD - Display header information (eg size of a file before you load it down)
OPTIONS - Return of methods that are available on a resource. - Allow the different representation (also called content negotiation), such as XML or JSON string
- the stateless communication as it is in the HTTP protocol specifies.
What are the advantages of REST?
- universal support in any language (eg Java, C, Perl, PHP, Ruby, C #,. NET ...) and many tools (such as wget, curl)
- A very good scaling
- real web integration, through the full utilization of HTTP status codes, including its
- XML support, but also other formats such as JSON (JavaScript Object Notation
However, as applications can be implemented with REST support with JAVA?
Answer: by the Java Specification Request (JSR) number 311, which is to specify a Java API for RESTful Web Services. Stefan Tilkov takes an active part in this Spezikation, the reference implementation JERSEY exists currently in version 0.7.
Is a web framework that implements the Java environment REST very well GRAILS .
That it is worthwhile to deal with RESTful shown by the fact that Google is in the process many of its SOAP interfaces (eg for searches ) REST-based implementation.
The term REST buzzing for quite some time through the Internet. But what exactly REST is and how to implement REST using Java? This question has been adopted in the JAX session "Java API for RESTful Web Services" by Stefan Tilkov Innoq and explained to me very naturally. Below I would like to briefly summarize the most important thing for me this session and hope that the entire slides vn Stefan Tilkov can be downloaded from the JAX website soon. But back to REST. If you look around the internet a bit to REST, REST, there are many comparisons with other techniques, such as REST vs. SOA, REST vs.. SOAP and REST vs. WS-* (short for the rather wide range of standards in the web environment). According to Stefan Tilkov REST is comparable to the best of web services, but rather about his experiences, a different approach to high-level SOA to achieve goals. Originally, the term REST (Representational State Transfer) from a dissertation by Roy Fielding (see wikipedia) will use the current term but more in terms of the full "RESTful" use the Hypertext Transfer Protocol (HTTP) is used. After Tilkovs statements that can be REST reduced to five basic points: all things have an ID, technically implemented through the Internet unique URI things are interconnected, the use of standard methods (uniform interface), technical methods of HTTP GET - for obtaining optionally cached information PUT - create or modify a known ID POST - Create or attach a sub-resource (sub-resource) DELETE - (logical) deletion HEAD - Display header information (eg size of a file before you load them down) OPTIONS - Returns of methods that are available on a resource. Allow the different representation (also called content negotiation), such as XML or JSON string of stateless communication as it is in the HTTP protocol specifies. What are the advantages of REST? universal support in any language (eg Java, C, Perl, PHP, Ruby, C #,. NET ...) and many tools (such as wget, curl) A very good scaling real web integration, through the full utilization of HTTP, together with its status code support for XML, but also other formats such as JSON (JavaScript Object Notation But how applications can be implemented with REST support with JAVA Answer: by the Java Specification Request (JSR) number 311, which is a Java API for RESTful web services should be specified. Stefan Tilkov takes an active part in this Spezikation whose reference implementation JERSEY exists currently in version 0.7. A Web framework that implements the Java environment, REST is very good GRAILS. that it is worthwhile to deal with RESTful shown by the fact that Google is in the process many of its SOAP interfaces (eg for searches) REST based implementation.
gklinkmann written by \ \ tags: Grails , Java , JAX , net , networking , web2.0 , xml