| Page properties | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
Background
Previous assumptions about Iroha Network and Web API in general were usage of iroha-client with encapsulation of underlying (plain TCP) protocols.
New needs from dependent projects require discussion of these assumptions and decision how to work with iroha network.
...
Clients with only high level networking support (HTTP/WebSocket) need to do additional development for Iroha Bridge integration and may even have some runtime specific restrictions which will make it impossible.
High level solutions
- Iroha provides HTTP API out-of-the-box
- Need to define scope
- Need to not duplicate peer to peer communications logic
- Iroha Bridge module provides HTTP wrapper on top of Iroha API (on the Peer side)
- Need to define scope
- Iroha Bridge has an additional application as a proxy on top of Iroha API (as a standalone app or service mesh)
- Every client is responsible for Adapters