07-25-2014 10:12 AM
@crossrulz wrote:
@REAL! wrote:
Isn't a state machine with a queue a QMH?
Not quite. There is a slight difference between a Queued State Machine and a Queued Message Handler. They look alike, but the QSM handles its own queue to go through states while the QMH just accepts commands from other threads through the queue.
I would say that the QSM is an extension of the state machine, and QMH is an extension of the QSM. Or, that's how I picture it in my mind's eye.
07-25-2014 10:30 AM
@billko wrote:
@crossrulz wrote:
@REAL! wrote:
Isn't a state machine with a queue a QMH?
Not quite. There is a slight difference between a Queued State Machine and a Queued Message Handler. They look alike, but the QSM handles its own queue to go through states while the QMH just accepts commands from other threads through the queue.
I would say that the QSM is an extension of the state machine, and QMH is an extension of the QSM. Or, that's how I picture it in my mind's eye.
I would not state it quite that way. A QSM is an extension of the Simple State Machine. You can say this since they still act very much the same. The QMH is in a different world. Unlike the state machines that cycle through states in a somewhat deterministic way, a QMH just sits there and does something when it is told. So you really can't call the QMH an extension of the state machine. The QMH is actually an extension of the Producer/Consumer.
Nothing like arguing over semantics...
07-25-2014 10:38 AM
@Dennis_Knutson wrote:
...but NI will also lose points for such a question on the exam.
We've been doing some internal CLAD reviews...that question's days are numbered. 😉
07-25-2014 01:06 PM
@crossrulz wrote:
@billko wrote:
@crossrulz wrote:
@REAL! wrote:
Isn't a state machine with a queue a QMH?
Not quite. There is a slight difference between a Queued State Machine and a Queued Message Handler. They look alike, but the QSM handles its own queue to go through states while the QMH just accepts commands from other threads through the queue.
I would say that the QSM is an extension of the state machine, and QMH is an extension of the QSM. Or, that's how I picture it in my mind's eye.
I would not state it quite that way. A QSM is an extension of the Simple State Machine. You can say this since they still act very much the same. The QMH is in a different world. Unlike the state machines that cycle through states in a somewhat deterministic way, a QMH just sits there and does something when it is told. So you really can't call the QMH an extension of the state machine. The QMH is actually an extension of the Producer/Consumer.
Nothing like arguing over semantics...
And, semantically speaking, we're having a discussion, not an arguement. 😉
Maybe that's why I never could quite resolve why they didn't really act the same. If I think about it, it does have a lot more in common with the producer/consumer.
07-25-2014 01:29 PM
@billko wrote:
@crossrulz wrote:
@billko wrote:
@crossrulz wrote:
@REAL! wrote:
Isn't a state machine with a queue a QMH?
Not quite. There is a slight difference between a Queued State Machine and a Queued Message Handler. They look alike, but the QSM handles its own queue to go through states while the QMH just accepts commands from other threads through the queue.
I would say that the QSM is an extension of the state machine, and QMH is an extension of the QSM. Or, that's how I picture it in my mind's eye.
I would not state it quite that way. A QSM is an extension of the Simple State Machine. You can say this since they still act very much the same. The QMH is in a different world. Unlike the state machines that cycle through states in a somewhat deterministic way, a QMH just sits there and does something when it is told. So you really can't call the QMH an extension of the state machine. The QMH is actually an extension of the Producer/Consumer.
Nothing like arguing over semantics...
And, semantically speaking, we're having a discussion, not an arguement. 😉
Maybe that's why I never could quite resolve why they didn't really act the same. If I think about it, it does have a lot more in common with the producer/consumer.
If you really want to think about it, head over to this LAVA thread.
07-25-2014 01:38 PM
@crossrulz wrote:
@billko wrote:
@crossrulz wrote:
@billko wrote:
@crossrulz wrote:
@REAL! wrote:
Isn't a state machine with a queue a QMH?
Not quite. There is a slight difference between a Queued State Machine and a Queued Message Handler. They look alike, but the QSM handles its own queue to go through states while the QMH just accepts commands from other threads through the queue.
I would say that the QSM is an extension of the state machine, and QMH is an extension of the QSM. Or, that's how I picture it in my mind's eye.
I would not state it quite that way. A QSM is an extension of the Simple State Machine. You can say this since they still act very much the same. The QMH is in a different world. Unlike the state machines that cycle through states in a somewhat deterministic way, a QMH just sits there and does something when it is told. So you really can't call the QMH an extension of the state machine. The QMH is actually an extension of the Producer/Consumer.
Nothing like arguing over semantics...
And, semantically speaking, we're having a discussion, not an arguement. 😉
Maybe that's why I never could quite resolve why they didn't really act the same. If I think about it, it does have a lot more in common with the producer/consumer.
If you really want to think about it, head over to this LAVA thread.
Sounds fun - and educational. What could be better? 🙂
Thanks!