Intent API provides the highest
level of access to Router's features. To use this API, all you
need is to have PeerDeviceNet (Router) installed on users devices
to gain the runtime support. Apps send normal android intents
using PeerDeviceNet specific action names and pack message data as
intent "extra" data items with PeerDeviceNet specific keys. All
the PeerDeviceNet action names are defined at
Router.Intent
class and "extra" data keys at
Router.MsgKey
class which you get when you add the client jar file to your
project.
PeerDeviceNet's IDL APIs define
purely asynchronous methods and callbacks. To access Router
services thru these apis, you can use client wrapper classes
RouterConnectionClient
and
RouterGroupClient
which also handle some common book-keeping for you. There is also
DeviceInfo
class and
NetInfo
class used at idl api which defines information about devices and
networks.
Messenger API is also a high level
api for apps using android's standard messaging pattern
"Messenger". This api defines a group of PeerDeviceNet specific
message ids which can be used with android's Message object. Apps
use messengers to send message data as a bundle with data items
using the same key names as Intent api. All the PeerDeviceNet
message ids are defined at
Router.MsgId
class and bundle data keys are defined in
Router.MsgKey
class.