On the other hand, has to respond to your ping by sending a pong message back via the same gateways as illustrated below:
#ANDROID STUDIO LAYOUTMARGINHORIZONTAL ANDROID#
Your app will look like this:Īs illustrated in the picture below, when you send a ping from your Android app to, the message will pass through the private gateway, then on to the public gateway (at, for example), and it'll then arrive at the public endpoint. Awala Ping is a hybrid service, but we'll use it as a centralised service here. You'll build an Android app that will send ping messages to the public endpoint at, and it'll also receive pong messages from said public endpoint. Alternatively, if there's a public endpoint involved in some but not necessarily all messages, then the service is hybrid.Īnyone can define Awala services, but to keep this codelab simple, we'll just build an Android app for Awala Ping, which is a trivial service used to test Awala itself.
The service is centralised if there's a public endpoint as the sender or recipient of all messages, or decentralised if all endpoints are private. Server-side apps exposed as Internet hosts will have public endpoints (e.g., ), whilst all other apps (e.g., mobile, desktop) will have private endpoints. Build an Android app for a centralised Awala serviceĪn Awala service is a collection of mobile, desktop, server-side and/or CLI apps that exchange mutually-intelligible messages using endpoints.
0 kommentar(er)
