| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Another reqrite... | Harald Eilertsen | 2023-03-29 | 1 | -113/+0 |
| | | | | | | | | | | | | | | | | | | | 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. | ||||
| * | Update reqwest and make async. | Harald Eilertsen | 2021-07-05 | 1 | -2/+2 |
| | | | | | | | | | 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... | ||||
| * | bin/zot: Clean up channel stream output somewhat. | Your Name | 2020-05-03 | 1 | -9/+18 |
| | | | | | Not really easy to find a goot pure text representation of this, though. | ||||
| * | Promote example app to proper command line client. | Your Name | 2020-05-03 | 1 | -0/+104 |
 |
index : rust-zotapi.git | |
| Zot API wrapper in Rust. | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |