Hi, When it comes to excluding dissectors I have been toying with an idea of dissector groups where you can disable a whole group of dissectors like telco, financial, zigbee etc. Starting to look at the dissector disabling code yesterday I'm wondering if disabling should happen earlier and not registering hfs tex.
The groups could be made in cmake too I suppose. If you want to compile a subset of dissectors. Best regards Anders Den tors 13 nov. 2025 09:28Tomasz Moń <[email protected]> skrev: > On Wed, Nov 12, 2025 at 4:13 PM Michael Mann via Wireshark-dev > <[email protected]> wrote: > > What I want is feedback from the dev-list on where to go from here. Do > people like the idea? Should "epan.lib" be more formalized? > > I like the idea of decoupling dissection engine away from UI. My wish > would be to be able to separate the processing into threads. While > multithreading dissection may be impossible due to inter-packet > dependencies, just separating dissection away from UI should give some > benefits. > > Initially I would like to see just the dissection engine running in > its own thread, with the synchronization achieved with a mutex. This > alone would be quite challenging, but is a first step towards parallel > processing. > _______________________________________________ > Wireshark-dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ Wireshark-dev mailing list -- [email protected] To unsubscribe send an email to [email protected]
