[bisq-network/bisq] Minimal api (#3001)

[Bernard Labno]

>@blabno I think you did what is truly the best practice in a usual context of startups building nice API-s.
>It's just that Bisq is not that usual context.

What added value does this bring into this conversation?

>And no, dependencies do need to be upgraded all the time

Doesn't this contradict that "unusual context" statement. 

>pricenode already offers a simple HTTP API within existing aggregated dependencies in the project (gradle-witness)

Are you sure about that gradle-witness part?

>how about starting with a dumbest RESTful API possible based on that? 

I've spent over a year going back and forth with this API stuff, trying different approaches.
The devil is in the details. You can pick some random single jar library to produce "Hello world" but further down the road you will find out that you miss a lot of features and that tiny lib you've picked is buggy as hell.


-- 
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/bisq/pull/3001#issuecomment-524768006
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190826/b1fe8084/attachment-0001.html>