CODEWITHSUNDEEP
c#c++delphiconsole
Mick
Mick

Reputation: 13495

What is a good format for command line output when it is being used for further processing?

I have written a console application in Delphi that queries information from several locations. This application will be launched by another process, and the output to STDOUT will be captured by the launching process.

The information I am retrieving is to be interpreted by the calling application for reporting purposes. What is the best way to output this data to STDOUT so that it can be easily parsed? JSON? XML? CSV? The data, specifically, is remote workstation information, so it will pull things back like running processes, and details about each process.

Does anyone have any experience with this or suggestions?

Upvotes: 1

Views: 305

Answers (4)

mjn
mjn

Reputation: 36684

The XML output format has the advantage that you can pipe it to a XSL formatter, so that the XML data can be converted to a user friendly HTML document. (You can almost have the cake and eat it too) ...

Upvotes: 0

John Thomas
John Thomas

Reputation: 4133

I'd go for a Tab-delimited file, if your data (as it seems) doesn't contain that character because it allows the fastest and simplest processing. All the other formats are slower and more complicated (even if they give you more power).

The closest match is CSV but CSV needs to quote the item if the item contains some special characters defined by the CSV (space, comma, quotes etc.).

Because of the above thing, the Tab delimited format is the most compact one, hence it has the greatest speed over-the-wire. (Since you're talking about remote workstations I assume that you're on some kind of network).

Also, another thing worth mentioning is that the Tab delimited format is very readable thus making the debugging much easier, if needed.

As an aside, if the Tab character is present in your data stream you can choose another character which you are sure that cannot be. (For example #1 etc.). Of course, this if your usage scenario permits it.

HTH

Upvotes: 5

Zoë Peterson
Zoë Peterson

Reputation: 13332

It would depend entirely on what the launching process has available. If it's a small Delphi app, CSV is easy to parse with just TStringList. XML may be more heavy weight than JSON, but Delphi ships with an XML parser, and AFAIK, not a JSON parser.

Upvotes: 0

Mason Wheeler
Mason Wheeler

Reputation: 84650

If you want something that can be easily parsed, especially if it has to be done quickly, go with the simplest format that can effectively communicate the information you need. CSV if you can, otherwise try JSON. Definitely not XML unless you really, really need all the extra complexity for some reason.

Upvotes: 6

Related Questions