2 of 5

Implementation

Any implementation bridges a gap. There is an API on one side. That API describes features. It was created to serve use cases. This API will be used by a (graphical) user interface. That API has its roots in the application domain.

Each implementation is based on other software. That is the other side. In our case, that software is mainly ASAP.

Our implementation has to transform API calls into ASAP calls and vica versa. Our implementation must transform application data structures into ASAP structures and vice versa.

• [SharkMessage de-/serialization](#SharkMessage de-/serialization)

SharkMessage de-/serialization

We defined our message datstructure with an interface: SharkMessage.

ASAP allows sending messages: sendASAPMessage. This methode requires three parameter: An application format an optional URI and a byte array that contains the actual content.

InMemoSharkMessage is the class that bridges that gap.

Send messages

Receive messages