[bisq-network/proposals] Integrate HTTP API to bisq-network (#22)

Manfred Karrer notifications at github.com
Wed May 30 23:46:29 UTC 2018


I started to add 2 projects to Bisq [1,2] and added basic setup for a BisqDaemon [3] and a new DesktopMain [4] class which supports 2 new option keys: desktopWithHttpApi and desktopWithGrpcApi.

I think it is cleaner to use a separate main class [5] for the HTTP-API-only (headless) case, so current plan is to not support the API-only version in the same main class which supports the combination Desktop + API. 
@blabno: If there are strong reasons why such would be required, please let me know, though it might not be that trivial as the JFXApplication is referenced in the Main class which would not work with the headless approach. I don't like to add hacks via reflection to circumvent that.... 

It is all WIP, but wanted to share early the direction....

[1] https://github.com/ManfredKarrer/bisq-grpc/tree/api-integration
[2] https://github.com/ManfredKarrer/bisq-http-api/tree/api-integration
[3] https://github.com/ManfredKarrer/bisq-core/tree/api-integration
[4] https://github.com/ManfredKarrer/bisq-desktop/tree/api-integration
[5] https://github.com/ManfredKarrer/bisq-http-api/blob/api-integration/src/main/java/bisq/httpapi/BisqHttpApiMain.java

-- 
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/22#issuecomment-393354639
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180530/080c5730/attachment-0002.html>


More information about the github mailing list