On Oct 22, 2003, at 2:21 PM, Adam Doppelt wrote:
I've written an http xml dissector plugin that pretty prints XML sent
as the
body of an HTTP request or response. It uses gmarkup to parse the XML.
If gmarkup is:
http://developer.gnome.org/doc/API/2.2/glib/glib-Simple-XML-Subset-
Parser.html
then:
1) the configuration script should check whether the g_markup routines
are available, and not build the plugin if they're not (so that
Ethereal will continue to build with GLib 1.2[.x]; was gmarkup present
in 2.0[.x]?);
2) note that it says "The "GMarkup" parser is intended to parse a
simple markup format that's a subset of XML. This is a small,
efficient, easy-to-use parser. It should not be used if you expect to
interoperate with other applications generating full-scale XML." - does
that mean that if the body contains features *NOT* supported by gmarkup
(the page in question lists them), it won't be properly parsed?
Also, when does that dissector get called? I.e., who determines that
the body is XML?
I'm not that familiar with the ethereal project... what's the best way
to
send the dissector to the list? There are a few files associated with
the
plugin, plus a couple of makefile changes to include the plugin in the
build.
As either
1) a gzipped tarball containing the files (including "diff -c" or
"diff -u" patches for the Makefile.am and Makefile.nmake changes - no
changes to Makefile.in or Makefile should be included);
2) attachments for each of the files in question (except for the
patches, which can be combined into one large patch file);
3) a URL to a gzipped tarball as per 1).
If you haven't done so already, please read the "Portability" section
of "doc/README.developer" and make sure you're not doing anything it
says not to do.
