Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

HIGH LEVEL INTERFACE?

April 26, 2017high interface level

0

Posted

HIGH LEVEL INTERFACE?

1 Answer

0

Posted

Open Transactions now supports a high-level interface. Here’s the breakdown of everything… OTLib The OTLib folder contains the core library, libOTLib.a, which includes most of the classes (but no transport code.) You can link to this static library, but most will not. (OTLib is the “low level interface.”) If you do, just include whatever headers you need from the OTLib folder. C API On top of that, the testwallet folder can be built either as a command-line test client (testwallet.exe), OR as ANOTHER library: libOTAPI.a, which includes the above lib PLUS the transport code and the C/C++ APIs. Whenever you link to this static lib, include OTAPI.h for the C functions, and OpenTransactions.h for the C++ class. SWIG wrappers in various languages… You can also build the testwallet folder for other languages, like this: make -f Makefile.API LANGUAGE=perl5 TRANSPORT=XmlRpc make -f Makefile.API LANGUAGE=php5 TRANSPORT=XmlRpc make -f Makefile.API LANGUAGE=java TRANSPORT=XmlRpc make -f Makefile.