On Fri, Jun 24, 2005 at 04:06:18PM +0200, Thomas Anders wrote:
> >TA> misleading.
> >
> >Right, but we could easily define a new one, with the same value, and use 
> >that
> >one in all the code (leaving the old one in the header for backwards
> >compatability).
> 
> Agreed. Steve, are you willing to incorporate this into your upcoming patch?

Sure. But you get to pick the name this time :-)

> I'm not sure I agree. Why require people to configure like this for the 
> whole toolkit when all they want is to configure like this for a certain 
> application instance? Why not even have a "noPersistentStore" config token?

I think it could go both ways.

Case #1: net-snmp is incorporated into the product-build tree, would be
helpful to just elide the config code entirely at compile time. Reduce
the size and complexity of the deliverable.

Case #2: project links with the NET-SNMP found on the current machine,
wants to turn off config (and MIBs). I am working on a project like
this; a security program of sorts that only talks *one* OID, so it will
be hardcoded. Others will link this against whatever library they have
lying around - no way I want to make them configure their own library.

I think there might be three options here:

        1) disable load of config
        2) disable load of persistent state
        3) disable save of persistent state

It seems to me that #2 and #3 should go toghteer, but I don't know if 
#1 and #2 share the same code for loading.

My work with NET-SNMP is more in the embedded space, so I'm very much for
eliding code at build time to lower the footprint. Granularity is good.

Would these ./configure options provide the right level of distinction?

        --disable-config-loading                # loads only
        --disable-persistent-state              # load + save

Steve

--- 
Stephen J Friedl | Security Consultant |  UNIX Wizard  |   +1 714 544-6561
www.unixwiz.net  | Tustin, Calif. USA  | Microsoft MVP | [EMAIL PROTECTED]


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to