port
- A C string (char *) which defines the port that RMR will
+ A C string (pointer to char) which defines the port that RMR will
open to listen for connections.
will complete and the program will exit as there is no code
following the instruction to create the object.
- Listening For Messages
- ============================================================================================
+Listening For Messages
+============================================================================================
The program in the previous example can be extended with just
a few lines of code to enable it to receive and process
registered callback for the message type will be invoked by
the framework.
- Callback Signature
- --------------------------------------------------------------------------------------------
+Callback Signature
+--------------------------------------------------------------------------------------------
As with most callback related systems, a callback must have a
well known function signature which generally passes event
it is not necessary to wait for RMR to receive a table from
the Route Manager.
- Registering A Default Callback
- --------------------------------------------------------------------------------------------
+Registering A Default Callback
+--------------------------------------------------------------------------------------------
The xApp may also register a default callback function such
that the function will be invoked for any message that does
callback is registered by providing a *generic* message type
of xapp->DEFAULT_CALLBACK on an Add_msg_cb call.
- The Framework Callback Driver
- --------------------------------------------------------------------------------------------
+The Framework Callback Driver
+--------------------------------------------------------------------------------------------
The Run() function within the Xapp object is invoked to start
the callback driver, and the xApp should not expect the
callback function will be invoked concurrently from multiple
threads.
- Sending Messages
- ============================================================================================
+Sending Messages
+============================================================================================
It is very likely that most xApps will need to send messages
and will not operate in "receive only" mode. Sending the
take one of two forms:
- +
+
$1 Replying to the sender of a received message
$1 Sending a message (routed based on the message type and subscription ID)
based on the mapping of the message type and subscription ID
using the current routing table known to RMR.
- Direct Payload Manipulation
- --------------------------------------------------------------------------------------------
+Direct Payload Manipulation
+--------------------------------------------------------------------------------------------
For some applications, it might be more efficient to
manipulate the payload portion of an Xapp Message in place,
Figure 7: Send message without buffer copy.
- Sending Multiple Responses
- --------------------------------------------------------------------------------------------
+Sending Multiple Responses
+--------------------------------------------------------------------------------------------
It is likely that the xApp will wish to send multiple
responses back to the process that sent a message that
necessary, the xApp must make a copy of the payload before
the first response call is made.
- Message Allocation
- --------------------------------------------------------------------------------------------
+Message Allocation
+--------------------------------------------------------------------------------------------
Not all xApps will be "responders," meaning that some xApps
will need to send one or more messages before they can expect
can be used to create a Message object with a desired payload
size.
- Framework Provided Callbacks
- ============================================================================================
+Framework Provided Callbacks
+============================================================================================
The framework itself may provide message handling via the
driver such that the xApp might not need to implement some
response, all it needs to do is to register its own callback
function for the health check message type.
- Example Programmes
- ============================================================================================
+Example Programmes
+============================================================================================
The following sections contain several example programmes
which are written on top of the C++ framework.
- RMR Dump xAPP
- --------------------------------------------------------------------------------------------
+RMR Dump xAPP
+--------------------------------------------------------------------------------------------
The RMR dump application is an example built on top of the
C++ xApp framework to both illustrate the use of the
Figure 8: Simple callback application.
- Callback Receiver
- --------------------------------------------------------------------------------------------
+Callback Receiver
+--------------------------------------------------------------------------------------------
This sample programme implements a simple message listener
which registers three callback functions to process two
Figure 9: Simple callback application.
- Looping Sender
- --------------------------------------------------------------------------------------------
+Looping Sender
+--------------------------------------------------------------------------------------------
This is another very simple application which demonstrates
how an application can control its own listen loop while
Code Review / ric-plt / xapp-frame-cpp.git / commitdiff