As you can see on above list, wodBeep supports two types of tuning profiles - ones that take control over complete wodBeep session, and ones that only take control over content that is sent through messages. Depending on your choice when you implement tuning profiles, you should be aware that:

SessionTuning needs to implement TuningSend and TuningReceive methods at raw level. When data arrives to be examined by your tuning profiles, there is no knowledge on what does data contain - it is not structured any any way. SessionTuning profiles MUST be started before any other non-SessionTuning profile. Once they complete, Beep session is restarted.

MessageTuning needs to implement Send and Receive methods at high level. Data arrives in Message format, and you should only change contents of the message. At raw level, Beep session is sending regular beep-structured messages, but their contents is changed by your tuning profile.

If NoTuning is selected, then profile does not implement any tuning, and is considered to be regular, exchange profile.