| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Third time must be where it sits I hope.
I felt the API was getting a bit too distracted by unnecessary
constructs and abstractions, so I'm trying to simplify it by making it
more straight forward.
The idea now is to have one main API class (ZotApi), and all the various
remote API's as public methods on this basic class. Iow, the ZotApi
class is mainly based on the existing `Client` class, which is then
being phased out.
And instead of having each API tied to the data type they return, I'm
just adding methods that will return the respective data types. This
should reduce coupling between the returned data, and the API calls
themselves.
|
|
|
|
| |
We don't really need the intermediate layer in the binary module.
|
|
|
|
|
|
|
|
| |
This means adding the full tokio as a dependency. While there isn't much
gain to going async in the current cli demo app, a full fledged app may
have more to gain by it.
First foray into async rust, so I might not do it right...
|
| |
|
|
|
|
| |
We want to have the XChan type for actial XChan data.
|
| |
|
|
|
|
| |
Also make constructor functions in the zotapi namespace.
|
| |
|
| |
|
|
|
|
| |
Simplifies serialization of various types quite a bit.
|
| |
|
|
|
|
|
|
|
|
|
| |
Since it only makes sence to fetch an xchan by one of the methods
(address, hash or guid) we don't need a data type that can hold more
than one value.
Had to implement my own serializer for it, since serde_urlencoded don't
know how to serialize enums by default.
|
| |
|
|
Not entirely happy with it, have updated the signature of
Client::fetch_stream and Client::url to take args, which are left out if
they're not serializable (or empty, I hope.) Should probably use an
Option instead, or maybe even two entry points for the api.
|