Template:FAQ:Coding 09 - Revision history

Dts12: Latest FAQ revision - preparing for 5.5 release

2009-07-20T19:41:06Z

Latest FAQ revision - preparing for 5.5 release

Dts12: 5.4 release synchronisation

2006-12-28T23:30:40Z

5.4 release synchronisation

Dts12 at 11:14, 23 October 2006

2006-10-23T11:14:45Z

New page

The answer to that heavily depends on the characteristics of the
MIB objects being implemented. Of the handler-based table frameworks,
<CODE>'tdata'</CODE> is more appropriate for tables that can be stored (or a copy
cached) within the agent itself, while <CODE>'iterate'</CODE> is more relevant to
reporting data from outside the agent.
The raw interface is only suitable in very specific circumstances,
so it's probably sensible to start with one of the other frameworks
first, and only look at this if none of the alternatives seem to work.

The decision between the handler-based configs and <CODE>MfD</CODE> is more a
matter of the style of programming to use. Most of the frameworks
define a single handler routine to process an incoming request, so
all of the code is listed together, with the MIB programmer inserting
table-specific processing into this single block of code.
The MfD provides a series of individual object-specific routines,
each concerned with one very specific task, and hides as much as
possible from the programmer.

If you like to understand the broad thrust of what's happening,
then one of the handler-based approaches would be the best choice.
If you prefer to concentrate on the nitty-gritty of a given table,
and are happy to trust that the rest of the processing will work
correctly, then the MfD framework would be more appropriate.

For implementing a group of scalar objects, then the choice is
simple - use <CODE>'mib2c.scalar.conf'</CODE>. Similarly, for generating traps
or informs, use <CODE>'mib2c.notify.conf'</CODE>.

← Older revision		Revision as of 19:41, 20 July 2009
Line 33:		Line 33:

	Similarly, for generating traps		Similarly, for generating traps
−	or informs, use <CODE>'mib2c.notify.conf'</CODE>.	+	or informs, use <CODE>'mib2c.notify.conf'</CODE>. But note that this only assists
		+	with the code to actually generate the trap. It does not address the
		+	issue of ''when'' to send the trap. See the FAQ entry
		+	[[FAQ:Coding_15\|How can I get the agent to generate a trap?]] for more information.

@@ Line 1: / Line 1: @@
 The answer to that heavily depends on the characteristics of the
 MIB objects being implemented.  Of the handler-based table frameworks,
@@ Line 24: / Line 30: @@
 For implementing a group of scalar objects, then the choice is
-simple - use <CODE>'mib2c.scalar.conf'</CODE>.  Similarly, for generating traps
+simple - use <CODE>'mib2c.scalar.conf'</CODE>.
 or informs, use <CODE>'mib2c.notify.conf'</CODE>.