phpWatch 2.0 Status

It has been a very long time since I’ve made a post and have received a great deal of e-mails inquiring about the status of phpWatch 2.0.  Classes have taken their toll on my free time for the last few months and I’m just now getting back to development.  My hope is that a beta version can be released within the next few months.  As for features and the current progress of major components, below is a short summary:

• Database Abstraction (100% complete): I’ve written a small database layer on my own rather than using something like ADOdb due to the limited scope of queries that must be run in phpWatch 2.0.  Implementing new storage methods (whether a different database type, file storage, etc.) requires writing only a few methods.
• Channels (90% complete): I’ve introduced the notion of channels in phpWatch 2.0.  A channel is simply a method by which notifications are sent.  Examples include e-mail, SMS, and TCP/UDP communications.  Each channel type implements its own callback which is triggered on service failure.  Implementing new channels is extremely simple.  One class must be extended and no database modification or other outside changes are necessary.
• Monitors (80% complete): Different types of monitors are also allowed in phpWatch 2.0.  Each type of monitor, like channels, implement a specific way of querying a specified service.  Examples include a raw socket check (as implemented in the existing phpWatch) and content verification which compare the result of a request with a known-correct response.  Like channels, monitor types can be easily added by developers to suit individual needs.
• Frontend (25% complete): The front-end of phpWatch 2.0 has been completely redesigned with a more user-friendly interface.  Per the requests of many, JavaScript usage is much more reserved to reduce load times on mobile devices.