http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2309
--- Comment #3 from LEGO <luis.ontanon@xxxxxxxxx> 2008-03-12 17:05:15 GMT ---
(In reply to comment #2)
> But did this work before we moved the UAT's from MIBS to Name Resolution?
>
No,
The UATs for mibs (others do not) are and were loaded during protocol
registration and that's when the mibs are loaded and the fileds registered.
Once the fields have being registered it would be relativelly easy to
increment. But, if there are changes in an eventually reloaded MIB (not likely
to happen but still it can be) it would be way too complicated to "rebuild" our
oids tree .
That would need:
Modify how UATs work to have a callback to be invoked whenever the UAT(s)
change (easy).
That callback would have to (re)initialize libsmi, register the fields
(ignoring already registered ones) AND take care of verifying that an OID has
not changed between reloads.
IMHO all that isn't worth, for the overwhelming mayority of people once the
settings have being made they'll stay there.
A note regarding the fact that SMI paths and modules are to be loaded only at
startup could be added to the tab where the UATs are linked.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.