Just to add my $.02, I'd rather see us using ASN.1 (and I absolutely
DETEST Asinine-1) than XML. Indeed, I'd like to see us come up with a
relatively-extensible binary format; if we're planning to use binary
for SQL, we might as well use it for flat-file as well. The fact that
data is being exploded by a factor of 6-10 is just unacceptable.
I'm certainly willing to put some of my protocol-design background to
use here, if that would help.
-derek
Dave Peticolas <[EMAIL PROTECTED]> writes:
> The binary format was really a dead-end. It was very brittle, with
> subtle endian and architecture issues, and continuing to extend it
> was going to be an extreme headache.
>
> That said, XML as the primary file store will probably be a transition
> solution on the way to embedded sql. Once we have that, the XML will be
> there as an export option, but a very well tested one :)
>
> dave
>
> _______________________________________________
> gnucash-devel mailing list
> [EMAIL PROTECTED]
> http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
