[bisq-network/proposals] Use a GRPC API as core API and use wrappers around for other API types (#136)

[Bernard Labno]

>The benefit it that GRPC is much faster and easier to add and require only 2 dependencies
Does that include transitive dependencies? Because last time I've checked there were like 15 or more transitive dependencies, which was almost the same as in case of HTTP API.

>Do you think you could adjust your HTTP API to become a wrapper around such a GRPC API?

In short yes. But the devil is in the details. The greatest challenge while working on HTTP API was untangling the core and desktop and making some of the core operations sort of stateless.

Apart from that, we've already had this discussion many times and it has been decided that we go with HTTP API. HTTP API has been ready for almost a year but delayed due to amount of code that needed to be reviewed. Finally we've got some initial version accepted into incubator.
The bottleneck are the maintainers. There is a bunch of PRs already prepared and waiting for being merged (and also blocking preparations of further PRs that depend on not merged PRs). 


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/136#issuecomment-552563211
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191111/308e1f21/attachment.html>