Hi!

I'm working on writing an XmpDetector for my Cartographer protocol.

I'm digging through the interface and abstract detector classes and
was wondering if you guys can answer some questions.

- If I understand it correctly, the basic interface of a detector is
  simply given an InetAddress and is asked "does that system have the
  protocol/service on it?"  I'm free to figure it out however I would
  like and I return true/false.  Is this a correct understanding?

- Is there one instance of an XmpDetector created for the entire
  running ONMS instance (like collectors) or are there many instances
  of XmpDetectors ?

- If the interface is that simple, do I need to bother to try to
  inherit from BasicDetector or SyncDetector?

- My protocol is synchronous; do I need to somehow declare that or let
  the creater of my detector know this?

- How do I glue my newly created XmpDetector back into the ONMS hive
  so that its invoked automatically?  I'm guessing some sort of
  etc/xml file?

(Once I get my detector developed and submitted, I'm going to get
working on integrating Cartographer/topography data.  I figured I'd
start with an XmpDetector as its been a while since I've
written/submitted to ONMS and figure it will take me a bit to re-learn
the code and architecture.)

Thanks,

Bobby

Attachment: pgpztz6lcpBYC.pgp
Description: PGP signature

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this 
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel

Reply via email to