TuningDataReceive notification is called by the transport when new data has arrived from remote peer, but is not yet parsed by the transport. It is used only by tuning profiles. wodBeep will pass this data to all tuning profiles currently active (through TuningProfiles collection). These profiles can change contents of this array, and even change its size.

For your own transport implementations: you should call this method when you want to notify your owner (wodBeep in most cases) that new data has been received from remote peer, and any tuning profiles currently running should be notified about it. These profiles MAY change data you have received, so you should always ignore data directly received from remote peer, and use data returned (in same argument) through TuningDataReceive notification.

Typical example would be SSL layer - if there's tuning profile active that provides SSL, whatever comes from the socket will be encrypted and unreadable by you. However, when you pass it through TuningDataReceive notification, proper tuning profile will decrypt it and return it back to you - so you can parse it to appropriate message and call MessageReceived notification.