Interoperability between protocols
In the announcement, there is an account of the obstacles that the Xpring team has gone through to develop the SDK. After receiving feedback from other developers on the APIs, Xpring was able to build a mature product and apply important API changes to the base code:Today, our libraries contain stable APIs and additional functionality (most notably: payment status and payment history). More notably, these libraries now connect directly to any rippled node, which lets dApp developers decentralize themselves from Xpring’s infrastructure and rely on their own nodes.
On the interlegder protocol (ILP), the project team has been able to incorporate code that allows users to connect to a remote ILP node and interact with the ILP protocol. Xpring outlines:The functionality makes heavy use of gRPC’s code generation which helped the team get code working, tested, QA’ed and delivered quickly in all variants of the SDK.
Support for the XPR Ledger also received component enhancements. For example, a feature was added to access payment histories and additional information about an account. The changes applied, says Xpring, have the benefit of having a common library that behaves the same across all the libraries used by the team.
作者 : Reynaldo