There are some missing features of ControlCarbonMessage right now. Now it only include byffer for data and boolean to identify the final fragment of those data.
But there can be different kind of controlling signals.

Ex :

• Open
• Close
• Heartbeat

So for that, we need to add the control signal feature for ControlCarbonMessage.

Need to update carbon-kernel version to 5.2.0-m3 and carbon-feature-plugin version to 3.0.0

Add a description about carbon-messaging source repository.

• jacoco-maven-plugin from 0.8.0 to 0.8.4 dependencies #82
• maven-surefire-plugin from 2.21.0 to 2.22.2 dependencies #81

Since now the ControlCarbonMessage is a extend of BinaryCarbonMessage in makes the end application logic more complex when checking the instance and also this could make more unknown issues in the end applications.
ex: When we are using WebSocket in message processors we check the instance of it to check what kind of message it is. In that if someone checks the instance of BinaryCarbonMessage before ControlCarbonMessage then it will be identified as a BinaryCarbonMessage not a ControlCarbonMessage.

The current implementation of carbon-messaging does not support WebSocket messaging.
We need to add WebSocket support to carbon-messaging in order to decouple Carbon-Transport from WSO2 MSF4J.