RE: [Bacula-devel] Re: Async I/O ready :-)

[David B. <db...@si...>]

> > > restore is that it currently issues a big list with choices when 
> > > selected.  This list is rather complicated and changes 
> from time to 
> > > time, so if you have any ideas, I

One thing that might be helpful: perhaps consider implementing a "terse"
mode in the console that is intended only for program-to-program
communications, rather than trying to parse the output of the normal
bconsole stream, and providing a "set terse on" command and method for
exiting terse mode. 

Example possiblity: 

1. Connect to director as a console and authenticate. 

2. SET TERSE ON. Bacula responds with 200 Terse Mode Set, 301 Ready

3. Issue commands (thinking out loud): 

*CMD* -START <sessionid>
<sessionid> Text of command
*CMD* -END <sessionid>

4. Bacula responds: 300 Response follows
*RSP* -START <sessionid>
<sessionid> Response follows
*RSP* -END <sessionid> 
301 Ready

Exiting terse mode could be done by executing a SET TERSE OFF via the
command mechanism. The sessionid would allow multiple commands and responses
to share the same connection (would be handy for WWW interfaces where a
single machine may be serving multiple users, etc)

Bracketing the command and response are the critical bits, the response
could be structured in a more formal way.