2015-05-01 08:28:01 +02:00
|
|
|
// Copyright (c) 2014 The btcsuite developers
|
Reimagine btcjson package with version 2.
This commit implements a reimagining of the way the btcjson package
functions based upon how the project has evolved and lessons learned while
using it since it was first written. It therefore contains significant
changes to the API. For now, it has been implemented in a v2 subdirectory
to prevent breaking existing callers, but the ultimate goal is to update
all callers to use the new version and then to replace the old API with
the new one.
This also removes the need for the btcws completely since those commands
have been rolled in.
The following is an overview of the changes and some reasoning behind why
they were made:
- The infrastructure has been completely changed to be reflection based instead
of requiring thousands and thousands of lines of manual, and therefore error
prone, marshal/unmarshal code
- This makes it much easier to add new commands without making marshalling
mistakes since it is simply a struct definition and a call to register that
new struct (plus a trivial New<foo>Cmd function and tests, of course)
- It also makes it much easier to gain a lot of information from simply
looking at the struct definition which was previously not possible
such as the order of the parameters, which parameters are required
versus optional, and what the default values for optional parameters
are
- Each command now has usage flags associated with them that can be
queried which are intended to allow classification of the commands such
as for chain server and wallet server and websocket-only
- The help infrastructure has been completely redone to provide automatic
generation with caller provided description map and result types. This
is in contrast to the previous method of providing the help directly
which meant it would end up in the binary of anything that imported the
package
- Many of the structs have been renamed to use the terminology from the
JSON-RPC
specification:
- RawCmd/Message is now only a single struct named Request to reflect the fact
it is a JSON-RPC request
- Error is now called RPCError to reflect the fact it is specifically an RPC
error as opposed to many of the other errors that are possible
- All RPC error codes except the standard JSON-RPC 2.0 errors have been
converted from full structs to only codes since an audit of the codebase
has shown that the messages are overridden the vast majority of the time
with specifics (as they should be) and removing them also avoids the
temptation to return non-specific, and therefore not as helpful, error
messages
- There is now an Error which provides a type assertable error with
error codes so callers can better ascertain failure reasons
programatically
- The ID is no longer a part of the command and is instead specified at the time
the command is marshalled into a JSON-RPC request. This aligns better with
the way JSON-RPC functions since it is the caller who manages the ID that is
sent with any given _request_, not the package
- All <Foo>Cmd structs now treat non-pointers as required fields and pointers as
optional fields
- All New<Foo>Cmd functions now accept the exact number of parameters, with
pointers to the appropriate type for optional parameters
- This is preferrable to the old vararg syntax since it means the code will
fail to compile if the optional arguments are changed now which helps
prevent errors creep in over time from missed modifications to optional args
- All of the connection related code has been completely eliminated since this
package is not intended to used a client, rather it is intended to provide
the infrastructure needed to marshal/unmarshal Bitcoin-specific JSON-RPC
requests and replies from static types
- The btcrpcclient package provides a robust client with connection management
and higher-level types that in turn uses the primitives provided by this
package
- Even if the caller does not wish to use btcrpcclient for some reason, they
should still be responsible for connection management since they might want
to use any number of connection features which the package would not
necessarily support
- Synced a few of the commands that have added new optional fields that
have since been added to Bitcoin Core
- Includes all of the commands and notifications that were previously in
btcws
- Now provides 100% test coverage with parallel tests
- The code is completely golint and go vet clean
This has the side effect of addressing nearly everything in, and therefore
closes #26.
Also fixes #18 and closes #19.
2014-12-31 08:05:03 +01:00
|
|
|
// Use of this source code is governed by an ISC
|
|
|
|
// license that can be found in the LICENSE file.
|
|
|
|
|
|
|
|
package btcjson
|
|
|
|
|
|
|
|
import (
|
|
|
|
"encoding/json"
|
|
|
|
"fmt"
|
|
|
|
)
|
|
|
|
|
|
|
|
// RPCErrorCode represents an error code to be used as a part of an RPCError
|
|
|
|
// which is in turn used in a JSON-RPC Response object.
|
|
|
|
//
|
|
|
|
// A specific type is used to help ensure the wrong errors aren't used.
|
|
|
|
type RPCErrorCode int
|
|
|
|
|
|
|
|
// RPCError represents an error that is used as a part of a JSON-RPC Response
|
|
|
|
// object.
|
|
|
|
type RPCError struct {
|
|
|
|
Code RPCErrorCode `json:"code,omitempty"`
|
|
|
|
Message string `json:"message,omitempty"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// Guarantee RPCError satisifies the builtin error interface.
|
|
|
|
var _, _ error = RPCError{}, (*RPCError)(nil)
|
|
|
|
|
|
|
|
// Error returns a string describing the RPC error. This satisifies the
|
|
|
|
// builtin error interface.
|
|
|
|
func (e RPCError) Error() string {
|
|
|
|
return fmt.Sprintf("%d: %s", e.Code, e.Message)
|
|
|
|
}
|
|
|
|
|
|
|
|
// NewRPCError constructs and returns a new JSON-RPC error that is suitable
|
|
|
|
// for use in a JSON-RPC Response object.
|
|
|
|
func NewRPCError(code RPCErrorCode, message string) *RPCError {
|
|
|
|
return &RPCError{
|
|
|
|
Code: code,
|
|
|
|
Message: message,
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// IsValidIDType checks that the ID field (which can go in any of the JSON-RPC
|
|
|
|
// requests, responses, or notifications) is valid. JSON-RPC 1.0 allows any
|
|
|
|
// valid JSON type. JSON-RPC 2.0 (which bitcoind follows for some parts) only
|
|
|
|
// allows string, number, or null, so this function restricts the allowed types
|
2015-04-17 17:14:00 +02:00
|
|
|
// to that list. This function is only provided in case the caller is manually
|
Reimagine btcjson package with version 2.
This commit implements a reimagining of the way the btcjson package
functions based upon how the project has evolved and lessons learned while
using it since it was first written. It therefore contains significant
changes to the API. For now, it has been implemented in a v2 subdirectory
to prevent breaking existing callers, but the ultimate goal is to update
all callers to use the new version and then to replace the old API with
the new one.
This also removes the need for the btcws completely since those commands
have been rolled in.
The following is an overview of the changes and some reasoning behind why
they were made:
- The infrastructure has been completely changed to be reflection based instead
of requiring thousands and thousands of lines of manual, and therefore error
prone, marshal/unmarshal code
- This makes it much easier to add new commands without making marshalling
mistakes since it is simply a struct definition and a call to register that
new struct (plus a trivial New<foo>Cmd function and tests, of course)
- It also makes it much easier to gain a lot of information from simply
looking at the struct definition which was previously not possible
such as the order of the parameters, which parameters are required
versus optional, and what the default values for optional parameters
are
- Each command now has usage flags associated with them that can be
queried which are intended to allow classification of the commands such
as for chain server and wallet server and websocket-only
- The help infrastructure has been completely redone to provide automatic
generation with caller provided description map and result types. This
is in contrast to the previous method of providing the help directly
which meant it would end up in the binary of anything that imported the
package
- Many of the structs have been renamed to use the terminology from the
JSON-RPC
specification:
- RawCmd/Message is now only a single struct named Request to reflect the fact
it is a JSON-RPC request
- Error is now called RPCError to reflect the fact it is specifically an RPC
error as opposed to many of the other errors that are possible
- All RPC error codes except the standard JSON-RPC 2.0 errors have been
converted from full structs to only codes since an audit of the codebase
has shown that the messages are overridden the vast majority of the time
with specifics (as they should be) and removing them also avoids the
temptation to return non-specific, and therefore not as helpful, error
messages
- There is now an Error which provides a type assertable error with
error codes so callers can better ascertain failure reasons
programatically
- The ID is no longer a part of the command and is instead specified at the time
the command is marshalled into a JSON-RPC request. This aligns better with
the way JSON-RPC functions since it is the caller who manages the ID that is
sent with any given _request_, not the package
- All <Foo>Cmd structs now treat non-pointers as required fields and pointers as
optional fields
- All New<Foo>Cmd functions now accept the exact number of parameters, with
pointers to the appropriate type for optional parameters
- This is preferrable to the old vararg syntax since it means the code will
fail to compile if the optional arguments are changed now which helps
prevent errors creep in over time from missed modifications to optional args
- All of the connection related code has been completely eliminated since this
package is not intended to used a client, rather it is intended to provide
the infrastructure needed to marshal/unmarshal Bitcoin-specific JSON-RPC
requests and replies from static types
- The btcrpcclient package provides a robust client with connection management
and higher-level types that in turn uses the primitives provided by this
package
- Even if the caller does not wish to use btcrpcclient for some reason, they
should still be responsible for connection management since they might want
to use any number of connection features which the package would not
necessarily support
- Synced a few of the commands that have added new optional fields that
have since been added to Bitcoin Core
- Includes all of the commands and notifications that were previously in
btcws
- Now provides 100% test coverage with parallel tests
- The code is completely golint and go vet clean
This has the side effect of addressing nearly everything in, and therefore
closes #26.
Also fixes #18 and closes #19.
2014-12-31 08:05:03 +01:00
|
|
|
// marshalling for some reason. The functions which accept an ID in this
|
|
|
|
// package already call this function to ensure the provided id is valid.
|
|
|
|
func IsValidIDType(id interface{}) bool {
|
|
|
|
switch id.(type) {
|
|
|
|
case int, int8, int16, int32, int64,
|
|
|
|
uint, uint8, uint16, uint32, uint64,
|
|
|
|
float32, float64,
|
|
|
|
string,
|
|
|
|
nil:
|
|
|
|
return true
|
|
|
|
default:
|
|
|
|
return false
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Request is a type for raw JSON-RPC 1.0 requests. The Method field identifies
|
|
|
|
// the specific command type which in turns leads to different parameters.
|
|
|
|
// Callers typically will not use this directly since this package provides a
|
|
|
|
// statically typed command infrastructure which handles creation of these
|
|
|
|
// requests, however this struct it being exported in case the caller wants to
|
|
|
|
// construct raw requests for some reason.
|
|
|
|
type Request struct {
|
|
|
|
Jsonrpc string `json:"jsonrpc"`
|
|
|
|
Method string `json:"method"`
|
|
|
|
Params []json.RawMessage `json:"params"`
|
|
|
|
ID interface{} `json:"id"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// NewRequest returns a new JSON-RPC 1.0 request object given the provided id,
|
|
|
|
// method, and parameters. The parameters are marshalled into a json.RawMessage
|
|
|
|
// for the Params field of the returned request object. This function is only
|
|
|
|
// provided in case the caller wants to construct raw requests for some reason.
|
|
|
|
//
|
|
|
|
// Typically callers will instead want to create a registered concrete command
|
|
|
|
// type with the NewCmd or New<Foo>Cmd functions and call the MarshalCmd
|
|
|
|
// function with that command to generate the marshalled JSON-RPC request.
|
|
|
|
func NewRequest(id interface{}, method string, params []interface{}) (*Request, error) {
|
|
|
|
if !IsValidIDType(id) {
|
|
|
|
str := fmt.Sprintf("the id of type '%T' is invalid", id)
|
|
|
|
return nil, makeError(ErrInvalidType, str)
|
|
|
|
}
|
|
|
|
|
|
|
|
rawParams := make([]json.RawMessage, 0, len(params))
|
|
|
|
for _, param := range params {
|
|
|
|
marshalledParam, err := json.Marshal(param)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
rawMessage := json.RawMessage(marshalledParam)
|
|
|
|
rawParams = append(rawParams, rawMessage)
|
|
|
|
}
|
|
|
|
|
|
|
|
return &Request{
|
|
|
|
Jsonrpc: "1.0",
|
|
|
|
ID: id,
|
|
|
|
Method: method,
|
|
|
|
Params: rawParams,
|
|
|
|
}, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Response is the general form of a JSON-RPC response. The type of the Result
|
|
|
|
// field varies from one command to the next, so it is implemented as an
|
|
|
|
// interface. The ID field has to be a pointer for Go to put a null in it when
|
|
|
|
// empty.
|
|
|
|
type Response struct {
|
|
|
|
Result json.RawMessage `json:"result"`
|
|
|
|
Error *RPCError `json:"error"`
|
|
|
|
ID *interface{} `json:"id"`
|
|
|
|
}
|
|
|
|
|
|
|
|
// NewResponse returns a new JSON-RPC response object given the provided id,
|
|
|
|
// marshalled result, and RPC error. This function is only provided in case the
|
|
|
|
// caller wants to construct raw responses for some reason.
|
|
|
|
//
|
|
|
|
// Typically callers will instead want to create the fully marshalled JSON-RPC
|
|
|
|
// response to send over the wire with the MarshalResponse function.
|
|
|
|
func NewResponse(id interface{}, marshalledResult []byte, rpcErr *RPCError) (*Response, error) {
|
|
|
|
if !IsValidIDType(id) {
|
|
|
|
str := fmt.Sprintf("the id of type '%T' is invalid", id)
|
|
|
|
return nil, makeError(ErrInvalidType, str)
|
|
|
|
}
|
|
|
|
|
|
|
|
pid := &id
|
|
|
|
return &Response{
|
|
|
|
Result: marshalledResult,
|
|
|
|
Error: rpcErr,
|
|
|
|
ID: pid,
|
|
|
|
}, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// MarshalResponse marshals the passed id, result, and RPCError to a JSON-RPC
|
|
|
|
// response byte slice that is suitable for transmission to a JSON-RPC client.
|
|
|
|
func MarshalResponse(id interface{}, result interface{}, rpcErr *RPCError) ([]byte, error) {
|
|
|
|
marshalledResult, err := json.Marshal(result)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
response, err := NewResponse(id, marshalledResult, rpcErr)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
return json.Marshal(&response)
|
|
|
|
}
|