Re: DisMan Event MIB selection

This is a discussion on Re: DisMan Event MIB selection within the SNMP Coders forums, part of the Networking and Network Related category; On Tue, 08 Nov 2005 10:02:12 +0000 Dave wrote: DS> > But you've claimed that there ...


Go Back   Usenet Forums > Networking and Network Related > SNMP Coders

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 11-08-2005
Robert Story
 
Posts: n/a
Default Re: DisMan Event MIB selection

On Tue, 08 Nov 2005 10:02:12 +0000 Dave wrote:
DS> > But you've claimed that there are no backwards-compatibility issues,
DS>
DS> Not true.
DS> If you look at the message where I first reported my new implementation,
DS> that explicitly states that there *are* some backwards-compatibility
DS> issues. Mostly fairly minor (e.g. -i vs -I), but they are there.

Hmm... I just re-read the thread, and I didn't see any such caveats. I also
noticed that your original intent was to replace the original implementation.

Are there good reasons for the incompatibilities? Especially something like
-i vs -I, which seems like it would be trivial to fix.

DS> And the behaviour is subtly different as well (e.g. what notifications
DS> are sent when an explicit event is specified).

But does the behaviour do what the MIB says it should? It would be reasonable
to have different behaviour it the new behaviour was correct.

DS> > DS> That sounds good to me.
DS> > DS> But I'd also suggest that we revert to 'disman/event.h' for the
DS> > DS> new implmentation, and use 'disman/event-mib.h' to issue a warning
DS> > DS> about the existence of the two alternatives.
DS> >
DS> > I don't particularly like this option, but will bend to the will of the
DS> > people. I would argue that the header name for the old code should
DS> > indicated it is the old code.
DS>
DS> Like 'disman/old-event-mib' does, you mean?

I'm fine with that for the old stuff. I don't really like the idea of a new
third option for the new code, and breaking existing packages/build scripts. I
still think silently replacing is the way to go.

DS> > You're not going to easily get
DS> > people to use the new code if it isn't turned on easily
DS> > in the fashion they're used to.
DS>
DS> But the new code is being included by default. They don't
DS> *need* to turn it on - it'll be provided automatically.

But the people using the old implementation will be forced to change something
to even be able to configure.

--
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>

You are lost in a twisty maze of little standards, all different.


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 06:44 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0