aboutsummaryrefslogtreecommitdiff
path: root/content/json-rpc-tale-of-interfaces.article
diff options
context:
space:
mode:
Diffstat (limited to 'content/json-rpc-tale-of-interfaces.article')
-rw-r--r--content/json-rpc-tale-of-interfaces.article2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/json-rpc-tale-of-interfaces.article b/content/json-rpc-tale-of-interfaces.article
index 59875f1..6afdc8c 100644
--- a/content/json-rpc-tale-of-interfaces.article
+++ b/content/json-rpc-tale-of-interfaces.article
@@ -1,7 +1,7 @@
# JSON-RPC: a tale of interfaces
27 Apr 2010
Tags: json, rpc, technical
-Summary: Here we present an example where Go's [interfaces](https://golang.org/doc/effective_go.html#interfaces_and_types) made it easy to refactor some existing code to make it more flexible and extensible. Originally, the standard library's [RPC package](https://golang.org/pkg/net/rpc/) used a custom wire format called [gob](https://golang.org/pkg/encoding/gob/). For a particular application, we wanted to use [JSON](https://golang.org/pkg/encoding/json/) as an alternate wire format.
+Summary: How to use the net/rpc package's interfaces to create a JSON-RPC system.
Andrew Gerrand