[lttng-dev] Machine Interface

[Jonathan Rajotte]

> > Now for the machine interface syntax:
> >
> >   * Also, to avoid confusion we will use a different primary command for input and
> >     output machine interface.
> >		Ex: lttng machine <input>
> >		Ex: lttng --xml <output>

This should be :
		for MI input: lttng machine <input>
		for XML output: lttng <command> <command-option> --xml

--xml would be an option for each command
> 
>    I have a problem with the broken symmetry here.  If you have a command (e.g. 'machine') for input, why is it you have none for output?  What happens if, for instance, I type 'lttng --xml list -k'?  Am I going to get an xml-formatted list of kernel tracepoints to stdout?
>
The syntax would be: lttng list -k --xml
and the output would be an xml-formatted list of kernel tracepoints to
stdout.


> Daniel U. Thibault
> Protection des systèmes et contremesures (PSC) | Systems Protection & Countermeasures (SPC)
> Cyber sécurité pour les missions essentielles (CME) | Mission Critical Cyber Security (MCCS)
> R & D pour la défense Canada - Valcartier (RDDC Valcartier) | Defence R&D Canada - Valcartier (DRDC Valcartier)
> 2459 route de la Bravoure
> Québec QC  G3J 1X5
> CANADA
> Vox : (418) 844-4000 x4245
> Fax : (418) 844-4538
> NAC : 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
> Gouvernement du Canada | Government of Canada
> <http://www.valcartier.drdc-rddc.gc.ca/>
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Jonathan Rajotte Julien
Chargé de laboratoire INF1995
Membre MD6
Polytechnique Montréal