Re: [Wireshark-dev] rev 18935: /trunk/epan/ /trunk/epan/dissectors/: packet-dcerpc-epm.c packet-dcerpc.c packet-dcom-cba.c packet-dcom-remact.c packet-dcom-remunkn.c packet-dcom.c packet-dcom.h /trunk

we now have pe_tree_, with permanent allocation scope. we should use them for guid-name mappings instead of a hashtable. (and add a file holding global wellknown mappings like manuf does for well known ethernet prefixes) On 8/17/06, ronnie sahlberg [EMAIL PROTECTED] wrote: Yes. it would

Re: [Wireshark-dev] [Wireshark-commits] rev 18935: /trunk/epan/ /trunk/epan/dissectors/: packet-dcerpc-epm.c packet-dcerpc.c packet-dcom-cba.c packet-dcom-remact.c packet-dcom-remunkn.c packet-dcom.c

ronnie sahlberg wrote: we now have pe_tree_, with permanent allocation scope. A permanent scope may not be right for all kinds of UUIDs/GUIDs, as some of them will be generated dynamically in the protocol machine. I know of the IPID in DCOM (which has the same meaning as the optional