On 11/11/2015 08:36, Dmitry Yemanov wrote: > > However, choosing XML over JSON or vice versa is IMHO a way nowhere. > Whatever one we choose, half of users will be against the chosen format > and ask us to support the second one. So we should either support both > out of the box or somehow stack custom format generators as plug-ins.
Half of users will be against plug-ins too. :) I don't see the need to support ourselves with something already common in the industry: conversion of standard formats. If we choose XML, we can publish a schema (XSD) as well. This way it's easy to people to read that XML and transform (if needed) to something else. Most programming languages / frameworks today can read it. With a XML schema, one can automatically generate classes and read that data directly in memory structures. On the other hand, we still use rudimentary tools (lack of good libraries in our code), and ISQL may print this raw XML directly or will continue printing text? I do not know... Adriano ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
