WebRPC is now called HTTP-RPC. The name was changed for several reasons:
- 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”).
- 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.WebRPCServiceis noworg.httprpc.WebServicevellum.webrpc.WebRPCServletis noworg.httprpc.ResultDispatcherServletvellum.webrpc.sql.ResultSetAdapteris noworg.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.WebServiceProxyNote 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 WSWebServiceProxyJavaScript Client
WebRPCService is now WebServiceProxyThe API is otherwise unchanged. See the project site for more information.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}