Editing GWT (section)

===Server Communication===

====GWT RPC====
The GWT RPC framework makes it easy for the client and server components of your web application to exchange Java objects over HTTP. The server-side code that gets invoked from the client is often referred to as a service. The implementation of a GWT RPC service is based on the well-known Java servlet architecture. Within the client code, you'll use an automatically-generated proxy class to make calls to the service. GWT will handle serialization of the Java objects passing back and forth—the arguments in the method calls and the return value. GWT RPC services are not the same as web services based on SOAP or REST. They are simply as a lightweight method for transferring data between your server and the GWT application on the client.
In order to define your RPC interface, you need to write three components:

#Define an interface (StockPriceService) for your service that extends RemoteService and lists all your RPC methods.
#Create a class (StockPriceServiceImpl) that extends RemoteServiceServlet and implements the interface you created above.
#Define an asynchronous interface (StockPriceServiceAsync) to your service to be called from the client-side code.