new-ui, the console, and synchronization by the front end

Hi,

I'm looking into using the new-ui feature with CGDB.

Historically, CGDB would only use the standard console
and it would allow the user to send one command at a time
to gdb. CGDB would often issue it's own commands
between the user commands.

In the new-ui work flow, I believe I understand there
are now two communication channels to gdb.
- new-ui for CGDB to communicate with gdb using MI
- standard console for the user to communicate with gdb

Do I have this right? (If so, i have a few questions)

If the CGDB allows a command to get sent to the
new-ui channel and to the standard console:
- Does gdb run them at the same time or in series?
- Is there an ordering mechanism within gdb to determine
  which is executed first?
- Can CGDB hook into gdb to run commands between
  the user console commands? (For instance, 'up' in gdb doesn't
  produce an mi async command to tell you the source file
  position has changed. Annotate=1 will alert you of this.
  So CGDB may want to run -file-list-exec-source-file
  between each user command to get the new file position.)
- If not, CGDB historically would only allow one user command
  to be sent to GDB at a time. annotate=2,3 provided the
  console prompt hooks to determine when a new command was
  available. However, annotations produce a lot of issues
  and I would really like to get away from them permanently.

Any other general purpose feedback on this would be excellent!

Thanks,
Bob Rossi