On 10/20/2015 01:26 PM, Wietse Venema wrote: > I don't know if JSON is still cool these days, but > that would be a possibility.
The other option would be XML, but my personal preference would definitely be JSON, XML tends to involve more complex libraries and can just get out of hand quickly whereas JSON stays relatively simple and easy to use and parse. > I suppose that the same order of "records" be used in the external > stream. There is no good reason to complicate the implementation. It would (imo) be easier to stick to key/value pairs inside an object instead of an ordered array and specifically not document what order they might end up in. External programs should be able to parse them in any order and that would leave more flexibility to be able to add to the record in the future without sacrificing backwards compatibility. > Other record types might be added (DSN atributes, SMTPUTF8, etc.), > but a good program will ignore record types that it does not > understand. Agreed. Peter
