I added support for queued MDI execution; thanks to Jeff for helping.
queued MDI is implemented in Axis
to enable support for other UI's:
---------------------------------
pre-55d93a8f 'queueing worked' due to improper state tracking by task -
interp_state would always be reported as INTERP_IDLE regardless whether the
current MDI command was still executing or not, and UI's took interp_state ==
INTERP_IDLE to mean "it's ok to send an MDI command"
to properly test whether it's ok to queue another MDI command, the test now is:
either interp_state == INTERP_IDLE (meaning 'no command currently
executing') OR
emcstatus.task.queuedMDIcommands < queuelimit (meaning 'command currently
executing but place in the queue')
I'd appreciate hints from folks maintaining UI's whether supporting queued MDI
makes sense, and if so, hints wrt the code location where MDI input should be
enabled
the obvious case is touchy, I am clueless about the others.
- Michael
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
