After a long summer, it's time to start focusing on... something.
For today: it's Protocol Definition! Thankfully, the Content Creation Wiki has provided the answer I've been looking for, to a question I have not quite defined:
"What is the difference between a protocol and and an API?"
In short: An API is more 'vertical,' in nature, as it can make a protocol take on certain 'un-defined' properties; a protocol is a common space/language, which many API layers may wrap and concede to.
So, it seems as if I have opted to take on the learning of OMG-IDL (Open Model Group - Interface Definition Language) in order to plan the OpenT/Rx communications architecture. The goal is to allow media-agnostic, jitter-resistant, multi-layer, multi-class communications between a controlling element and the [tran|re]ceiver.
OMG, buy the way, is the group that brought you COBRA, and acts as Standards Keeper for UML... so how could IDL be wrong ?!?
