OK let me clarify a bit,
a quote from http://wiki.mikrotik.com/wiki/Manual:HTB
Priority
We already know that > limit-at > (CIR) to all queues will be given out no matter what.
Priority is responsible for distribution of remaining parent queues traffic to child queues so that they are able to reach > max-limit
Queue with higher priority will reach its > max-limit > before the queue with lower priority. 8 is the lowest priority, 1 is the highest.
Make a note that priority only works:
- for > leaf > queues - priority in > inner > queue have no meaning.
- if > max-limit > is specified (not 0)
This HTB “Priority” feature gives bandwidth.
Where as when one says “strict priority queue” - one should mean - a queue (tree) that sends priority packets out, while non-priority packets are put in a queue to be sent after the priority ones. Strict - this means that the priority packets will never wait for a non-priority packet. Even if we have huge loss with the non-priority stuff.
So a lot of answers can be given in this topic. A lot of clarity can be given.
Maybe even as a flash movie, the Janis factory example http://forum.mikrotik.com/t/strict-priority-queue/36875/31 could be used as a base. And still - more clarity is needed for how, when packets are decided to be dropped, to be queued, etc. - informaction that can be shown graphically.