The Electrode Native Bridge expose a public client surface that is consistent across all three platforms and allows requests and responses from any side:
Send Requests (and associated responses)
Register Requests handlers
Register/Unregister Event listeners
Request and Event messages are named to identify the Request or Event message type. The name is used to direct the messages to the associated receivers. For example, names for Request messages might be
getAllMovies. And for Event messages, a name might be
When an Event message is sent from any side, the Electrode Native bridge looks for all registered listeners for this event type. The Electrode Native bridge then sends the message to all registered listeners for that event type, independent of the side on which they are located.
Payloads for Requests, Responses, or Events can be primitive types, but the Electrode Native bridge also supports complex object payloads (full-fledged model classes).