Many users of Wireshark don't require all of the supported for their day-to-day 
tasks.  Has any consideration been given to providing threw the build process, 
to select the protocols required by the builder?

In my case, I can't remember the last time I used any decode but the 
Ethernet/IP/TCP stack with VoIP, MEGACO and some custom dissectors.  Token 
Ring, IPX, Vines, etc. don't have much use to me in my normal day.  While this 
is not true of everyone, if I could build a reduced protocol Wireshark it 
would, among other things be:

be smallerless code == lest chance of program faultsless memory requiredfaster 
to build
I could see a simple set of "classes" that each dissector would be placed prior 
to building.  By default all current dissectors would be either core or 
optional.

core == required dissectorsoptional == Dissectors that enhance and provide 
additional information for core dissectors header only == dissect only the 
"root" proto_tree and return.ignore == do not add to library, dll or plug-in 
tree.
Any thoughts anyone?  Perhaps this capability exists, in that case I apologize.

Alex Lindberg



      
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to