Hello,
The next version of JFFNMS is nearly at Release Candidate stage. I'm
just finding all the missing objects in the admin links and doing some
cleaning up.
To give you an idea what has been happening, a brief list of changes:
* pollers, consolidator and other engines are completely re-written
with a better separation of parent/child code.
* No need to register globals, all parameters are sanitized
* counter64 for SNMP interfaces, for high speed interfaces
* Better handling of snmp v2c
* sysObjectId checking for interface discovery, so JFFNMS won't bother
checking for Cisco OIDs on a Juniper device, for example.
The code has had an awful lot of just general cleaning up. I test it
now using E_STRICT errort reporting and it generally now runs silently.
The high speed counters are in a way implemented already, but the check
is SNMP v2c. The problem is the v2c code is a not too robust and also
v2c doesn't mean high speed counters. The next version will have a
specific poller group for those counters but unfortunately the change
may need to be made manually.
What's Next?
============
Once this version of code gets released, I'll be looking at changing the
internal structures again. It is likely I'll be introducing some sort of
structured framework. The problem is that JFFNMS does everything from
scratch, so I have to keep updating things that are not directly related
to what JFFNMS does, such as session handling and database access.
An example of a framework is CakePHP which is a framework written in
PHP, just like JFFNMS. The database, presentation and other associated
helpful functions are there and maintained by that group.
It also uses a MVC (model, view, controller) architecture, which JFFNMS
uses already (sort-of). It keeps the type of data and database (model)
separare from the application logic (controller) and what it looks like
on the website (view). This gives me a better structure to work with and
maintain; as side effect JFFNMS will in future work with any database
the underlying framework can handle; either now or in the future.
The admin screens are almost trivial to change over to this sort of
setup. The operational screens are a bit more work, but are just views.
I'm still unsure about where the engines will tap in.
If you know of other frameworks like CakePHP and you think JFFNMS could
use it, let me know as that next step is not set as yet.
- Craig
--
Craig Small VK2XLZ http://www.enc.com.au/ csmall at : enc.com.au
Debian GNU/Linux http://www.debian.org/ csmall at : debian.org
GPG fingerprint: 1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
jffnms-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jffnms-users
