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

Migrating from On-Prem to Cloud Middleware? Here’s what Aberdeen Group says leading companies should be considering. Brought to you in partnershp with Liaison Technologies

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.

    Is iPaaS solving the right problems? Not knowing the fundamental difference between iPaaS and iPaaS+ could cost you down the road. Brought to you in partnership with Liaison Technologies.

    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.

    THE DZONE NEWSLETTER

    Dev Resources & Solutions Straight to Your Inbox

    Thanks for subscribing!

    Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

    X

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

    {{ parent.tldr }}

    {{ parent.urlSource.name }}