2009/4/22 Giuseppe Modugno <[email protected]>: > So you mean to translate each GET request via SNMP > into GET request via RS232.
Yup. That's the fundamental purpose of the SNMP agent. To accept management requests in a standard format (SNMP), and convert them into equivalent device-dependent requests. (be that an ioctl call, parsing a file from /proc, pulling data out of the kernel, or whatever). Most of the time, this is handled purely within the agent itself. The only difference here is that you're moving part of this device-dependent interface processing into a intermediate layer, so that the HTTP interface can use it too. > Anyway is this "simple common library" a third application that > communicates (by IPC/RPC/shared memory/...) with web server and snmp > agent, or is it a library, statically/dynamically linked with snmp > agent and web server? It's your management task - you can choose how you wish to implement it. Personally, I'd be inclined to start by writing a library that can be used with each management interface individually. That's probably a somewhat simpler coding task. If you find that doesn't meet your needs, then you can always replace this with an equivalent API to talk to a standalone third application. As long as the API stays the same, you shouldn't need to touch the SNMP agent or web server (apart from recompiling or relinking with the new library). Dave ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
