From: Paul Koning <pkoning@equallogic.com>
To: eliz@gnu.org
Cc: gdb@sourceware.org
Subject: Re: Using XML in GDB?
Date: Fri, 27 Jan 2006 19:06:00 -0000 [thread overview]
Message-ID: <17370.26869.663043.743656@gargle.gargle.HOWL> (raw)
In-Reply-To: <u64o5edeh.fsf@gnu.org>
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Fri, 27 Jan 2006 13:04:29 -0500 From: Daniel Jacobowitz
>> <drow@false.org>
>> ...The biggest win of XML, for me, is that there are standard answers
>> to all of these problems and standard tools for editing and
>> checking XML files.
Eli> Is XML the only widely used standard that supports what we want?
No, it isn't.
You're essentially asking for an easily extensible, flexible
protocol. XML is one of those; it is the extremely verbose end of the
"make it all ASCII" approach used in the Internet for decades. Then
again, the same is true for the existing remote stub protocol.
Another extensible protocol that comes with definition tools and
checkers, but is much more compact, is SNMP. Or, more precisely,
ASN.1 (the definition language) and BER/DER (the encoding rules).
If one of the goals is bit efficiency of the encoding, rather than
maximum verbosity, then ASN.1/DER is far better than XML. Chances are
the implementation would be smaller, too.
Just a thought about a rather different approach to the problem...
paul
next prev parent reply other threads:[~2006-01-27 18:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 7:01 Daniel Jacobowitz
2006-01-26 12:45 ` Andrew STUBBS
2006-01-26 13:41 ` Daniel Jacobowitz
2006-01-26 16:24 ` Andrew STUBBS
2006-01-26 16:41 ` Daniel Jacobowitz
2006-01-26 17:34 ` Paul Koning
2006-01-26 17:44 ` Andrew STUBBS
2006-01-26 18:55 ` Daniel Jacobowitz
2006-01-26 21:05 ` Mark Kettenis
2006-01-26 21:26 ` Daniel Jacobowitz
2006-01-26 21:57 ` Mark Kettenis
2006-01-26 22:02 ` Daniel Jacobowitz
2006-01-26 22:32 ` Bob Rossi
2006-01-26 20:39 ` Mark Kettenis
2006-01-26 20:43 ` Bob Rossi
2006-01-26 21:41 ` Mark Kettenis
2006-01-26 20:52 ` Daniel Jacobowitz
2006-01-26 21:12 ` Bob Rossi
2006-01-27 0:47 ` Bob Rossi
2006-01-27 18:04 ` Eli Zaretskii
2006-01-27 18:41 ` Daniel Jacobowitz
2006-01-27 18:57 ` Eli Zaretskii
2006-01-27 19:06 ` Paul Koning [this message]
2006-01-28 6:33 ` Daniel Jacobowitz
2006-01-28 13:54 ` Jim Blandy
2006-01-29 4:09 ` Eli Zaretskii
2006-01-29 4:27 ` Paul Koning
2006-01-28 5:24 ` Daniel Jacobowitz
2006-01-29 4:33 Paul Schlie
2006-01-29 6:18 ` Jim Blandy
2006-01-29 23:21 ` Daniel Jacobowitz
2006-01-29 23:24 ` Paul Schlie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17370.26869.663043.743656@gargle.gargle.HOWL \
--to=pkoning@equallogic.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox