-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 21 Aug 2003, Ronnie Sahlberg wrote: [snip] > The difficult part is those parts that can not be described in a generic > packet/interface description language such > as how and what state should be maintained between packets. How packets > relate to eachother. > What information should go in COL_INFO.
Maybe the problem should be broken down into multiple languages. One to describe packets, so that one can refer to the objects of interest in the packet-stream. Another to describe the relationships among packets. Another, Ethereal-specific, to map objects and relationships onto the user interface. "Ewww, I have to learn *three* languages? I wasn't sure I wanted *one*." Well, would you rather have PL/I, or FORTRAN and COBOL? (Actually I like PL/I, but that's another story....) Come to think of it, COBOL might be worthy of study here, not because it fits the problem domain(s) but because it's an example of a coherent language that's composed of several sublanguages which are aimed at different aspects of the overall problem. (I'm thinking of the various DIVISIONs: environment, data, procedure, etc.) A framework within which there are separate sublanguages to describe the static, dynamic, and presentational aspects of protocols might be a good place to end up. - -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] MS Windows *is* user-friendly, but only for certain values of "user". -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: pgpenvelope 2.10.2 - http://pgpenvelope.sourceforge.net/ iD8DBQE/RNves/NR4JuTKG8RAiOKAJ9YHSpVQvur7GyDR3K0X2zpbpPOewCdFrJz xTlL/jr/cfQhF2+t/AJ4MN8= =V3em -----END PGP SIGNATURE-----
