Hi,
> -----Original Message-----
> From: ethereal-dev-bounces@xxxxxxxxxxxx
> [mailto:ethereal-dev-bounces@xxxxxxxxxxxx]On Behalf Of Ulf Lamping
> Sent: giovedi 27 gennaio 2005 9.59
> To: Ethereal development
> Subject: Re: [Ethereal-dev] PDML Parsers?
>
>
> Fulvio Risso wrote:
>
> >NetBee (www.nbee.org) contains a class (nbPDMLReader) for PDML parsing;
> >there's also a small example for that.
> >However, how may need to change something, since PDML generated
> by Analyzer
> >and PDML generated by Ethereal contains small differences.
> >
> >
> If there are differences between PDML output of Analyzer and Ethereal
> (and I do think there are) this was by accident, not by intend.
>
> When I remember this correct, I've implemented this export some time
> ago, using the spec at the Analyzer homepage. Unfortunately while trying
> to import an Ethereal generated PDML into Analyzer, it didn't gave me
> good hints what was wrong with my file :-(
This is a problem on the Analyzer side.
In order to show packets, it needs also the PSML to display packet summary.
However, I had no time to implement the code that does this.
> If you know the differences and if there is a way to solve this, I would
> like to make them compatible.
There are two differences:
- the protocol called "frame"
- fields are named "protocol.fieldname", while Analyzer uses "fieldname"
only.
On both issues, I had to time to thing about what's the best choice.
So, let's wait ;-)
For instance, I've made a test right now: the NetBee library is able to read
PDML files generated by Ethereal without any problem.
fulvio