John McDermott wrote:
>
> 1) If there were a lot of protocols added dynamically, mightn't the startup
> time be long? That is, if the program had to parse a few zillion lines of
> protocol before doing any captures, this might take some time.
Of course, this should be an optional feature, i.e. the user has to specify
a protocol definition file to parse (via argument or preferences...).
So no startup time increase (except maybe the test of file opening ;-)
> This could be
> alleviated by using the dynamic parsing primarily for development and then
> encouraging folks to add compiled versions when the decoding is mostly stable.
And what about some internal (or proprietary) protocols you may have to
handle with. One would have to adapt his code at each new release since
I do not think you (and I) will accept any undocumented protocol in
ethereal ... (or I will commit my own internal protocols, that will save
a lot of my time :-)
> This would probably necessitate two versions of the parser: one for the
> built-in and one for generating some sort of code which could be
> compiled.
That would be two completely different approaches and developments but
this is a good idea.
Laurent.
--
Laurent DENIEL | E-mail: deniel@xxxxxxxxxxx
Paris, FRANCE | laurent.deniel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
| WWW : http://www.worldnet.fr/~deniel
All above opinions are personal, unless stated otherwise.