Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

WebRPC is Now HTTP-RPC

DZone's Guide to

WebRPC is Now HTTP-RPC

WebRPC is no more: it's HTTP-RPC now. Along with the name change are a few class name alterations, including Java server and Java client.

· Integration Zone
Free Resource

The Integration Zone is brought to you in partnership with Cloud Elements.  What’s below the surface of an API integration? Download The Definitive Guide to API Integrations to start building an API strategy.

WebRPC is now called HTTP-RPC. The name was changed for several reasons:

  1. The previous name suggested that it was a tool for web (i.e. HTML) development, not cross-platform RPC. It was also easily confused with WebRTC (“Real-Time Communication”).
  2. The webrpc.org domain was not available, but httprpc.org was.

The new name more clearly reflects the project's purpose: “cross-platform RPC over HTTP.”

Several class names were also changed:

Java Server

  • vellum.webrpc.WebRPCService is now org.httprpc.WebService
  • vellum.webrpc.WebRPCServlet is now org.httprpc.ResultDispatcherServlet
  • vellum.webrpc.sql.ResultSetAdapter is now org.httprpc.sql.ResultSetAdapter

Additionally, the vellum.webrpc.Result class has been repurposed as org.httprpc.beans.BeanAdapter. This class wraps an existing Bean object, rather than requiring the Bean to extend a specific type. It also provides parity with ResultSetAdapter, which wraps a result set.

Finally, the static map factory methods defined by the vellum.webrpc.Arguments class were moved to WebService.

Java Client

  • vellum.webrpc.WebRPCService is now org.httprpc.WebServiceProxy
  • Note that this change makes it possible to use both the Java Server and Java Client libraries in a single application. This was previously not possible because the libraries both used the name vellum.webrpc.WebRPCService to refer to two different classes.

    Objective-C/Swift Client

  • WSWebRPCService is now WSWebServiceProxy
  • JavaScript Client

  • WebRPCService is now WebServiceProxy
  • The API is otherwise unchanged. See the project site for more information.

    The State of API Integration Report provides data from the Cloud Elements platform and will help all developers navigate the recent explosion of APIs and the implications of API integrations to work more efficiently in 2017 and beyond.

    Topics:
    rpc ,http

    Published at DZone with permission of Greg Brown, DZone MVB. See the original article here.

    Opinions expressed by DZone contributors are their own.

    {{ parent.title || parent.header.title}}

    {{ parent.tldr }}

    {{ parent.urlSource.name }}