[SNMP4J] Extending Agent

[Frank Fock]

Hi David,

You should be able to register a UDP Transport mapping
on a different port. However, you cannot register
the transport mapping with the MessageDispatcher, because
the MessageDispatcher assumes that the data exchanged
is SNMP (BER).

Best regards,
Frank

Best regards,

dhay at lexmark.com wrote:
> 
> Hi Frank,
> 
> I'll like to extend it to support our propiertary protocol which uses 
> UDP but on a different port.
> 
> However, I got stuck registering two transportMappings for UDP with 
> different ports?  Can I get around this?
> 
> cheers,
> 
> David
> 
> 
> 
> *Frank Fock <fock at agentpp.com>*
> 
> 10/29/2007 04:04 PM
> 
> 	
> To
> 	dhay at lexmark.com
> cc
> 	snmp4j at agentpp.org
> Subject
> 	Re: [SNMP4J] Extending Agent
> 
> 
> 	
> 
> 
> 
> 
> 
> Hi David,
> 
> Although SNMP4J-Agent is specifically designed for SNMP,
> it can also be used to support other protocols. JMX is
> one of it.
> 
> The hinge-points could be the MOServer and ManagedObject
> interfaces. I could give more details if you give me more
> details on the protocol/technology in mind.
> 
> Best regards,
> Frank
> 
> dhay at lexmark.com wrote:
>  > Is everything in the SNMP4J Agent SNMP-specific?  Or could I feasibly
>  > extend it to support other protocols?  If so, where are the hinge-points?
>  >
>  > cheers,
>  >
>  > David
>  > _______________________________________________
>  > SNMP4J mailing list
>  > SNMP4J at agentpp.org
>  > http://lists.agentpp.org/mailman/listinfo/snmp4j
> 
> --
> AGENT++
> http://www.agentpp.com
> http://www.mibexplorer.com
> http://www.mibdesigner.com
> 

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com