TuningDataSend notification is called by the transport when there is data that will be sent to remote peer. Since this data is received by wodBeep, and typically contain BeepMessage contents (but not limited to), transport should send it to remote peer. However, if there is any tuning profile currently active (and transport can NOT know that), transport calls this notification so such tuning profiles can encode the data property, as defined by their profile.

For your own transport implementations: you should call this method when you want to notify your owner (wodBeep in most cases) that new data will be sent to remote size, and any tuning profiles currently active should inspect it.

Typical example would be SSL tuning profile - when active, any data should be encrypted before it actually leaves our peer.