ipfs-cluster

History

Hector Sanjuan 1b3d04e18b Move all API-related types to the /api subpackage. At the beginning we opted for native types which were serializable (PinInfo had a CidStr field instead of Cid). Now we provide types in two versions: native and serializable. Go methods use native. The rest of APIs (REST/RPC) use always serializable versions. Methods are provided to convert between the two. The reason for moving these out of the way is to be able to re-use type definitions when parsing API responses in `ipfs-cluster-ctl` or any other clients that come up. API responses are just the serializable version of types in JSON encoding. This also reduces having duplicate types defs and parsing methods everywhere. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>	2017-02-09 16:30:53 +01:00
..
main.go	Move all API-related types to the /api subpackage.	2017-02-09 16:30:53 +01:00
Makefile	Make sure the commit string gets set. Fix PublicKey. Output JSON in cluster-ctl	2017-01-24 16:56:14 +01:00

Hector Sanjuan 1b3d04e18b Move all API-related types to the /api subpackage.

At the beginning we opted for native types which were
serializable (PinInfo had a CidStr field instead of Cid).

Now we provide types in two versions: native and serializable.

Go methods use native. The rest of APIs (REST/RPC) use always
serializable versions. Methods are provided to convert between the
two.

The reason for moving these out of the way is to be able to re-use
type definitions when parsing API responses in `ipfs-cluster-ctl` or
any other clients that come up. API responses are just the serializable
version of types in JSON encoding. This also reduces having
duplicate types defs and parsing methods everywhere.

License: MIT
Signed-off-by: Hector Sanjuan <hector@protocol.ai>

2017-02-09 16:30:53 +01:00

main.go

Move all API-related types to the /api subpackage.

2017-02-09 16:30:53 +01:00

Makefile

Make sure the commit string gets set. Fix PublicKey. Output JSON in cluster-ctl

2017-01-24 16:56:14 +01:00