The first chapter gives the reader a quick introduction to RESTful services and the most common PHP frameworks in use at the time of writing. I particularly enjoyed the section on the Zend framework due to the explanation of benefits over the other frameworks. The chapter also covers the very basics which include a detailed look at exactly what RESTful services means and what technologies are required to use and benefit from a RESTful architecture. The second chapter gives a quick run down of the various methods in use for consumption of data; these being Curl, several HTTP methods, processing data with XML, DOM, and SimpleXML. After those are covered there is a simple example of consuming services like Flickr using the previous methods. This transitions into many more examples of consuming real world services that any developer would find interesting and exciting for data mashups.

The real meat of the book starts in chapter four where we get into designing the resource utilization systems and then the resource clients in chapter five. Those topics basically go over the nuts and bolts of gathering data, manipulating it, updating it, as well as creating fresh data. We get more instruction and usage examples on the Zend framework in chapter seven where the author gives us information on the controllers, models, and view (MVC model). This would not be too useful without knowing how to debug the code that we’re using so there is, thankfully, a chapter dedicated to debugging XML building and parsing errors. A couple of short appendixes cover the author’s own WSO2 web service framework as well as REST Client Classes which should prove useful for writing your own reusable classes.

Overall this book covers the majority of topics that a new developer needs to understand in order to start developing and deploying RESTful code and web services in PHP. From frameworks to consumable service samples, and everything in between, RESTful PHP Web Services comes through in a concise and enjoyable style that will not disappoint. I highly recommend this book for developers that are new to this topic or experienced developers that need a quick refresher course.

So my header.php code ended up looking like so:

$pages = wp_list_pages('sort_column=menu_order&title_li=&echo=0&exclude=377');
$pages = preg_replace('%]+)>%U','', $pages);
$pages = str_replace('','', $pages);
echo $pages;
?>


Model: http://themattreid.pastebin.com/fd163b0
View: http://themattreid.pastebin.com/f2a14ba54
Controller: http://themattreid.pastebin.com/f40599353

• Variable interval polling of server statistics
• Over 50 different alerts (see list below)
• Graphing of various server statistics (see list below)
• Tuning recommendations with cnf file changes to apply to server
• Change control documents for recommended performance/security tuning
• Threshold based alerting with multiple alert groups: info,warn,critical
• Sorting/ordering of servers via groups. ie: client -> dev,stage,prod
• RSS feeds for each alert group
• XML export with user defined fields for external applications (API of sorts)
• Slave server alerts, IO thread / SQL thread, seconds behind master (with threshold)
• Various general stats: version, system ram size, # of schema, default table type
• Ability to view current cnf file from server
• Ability to view current global variables as a list
• Email / pager reporting for alerts (choose warn/crit alerts to report on)

Alerts - can be enabled or disabled for reporting on a per server basis

• number of connection failures (threshold)
• number of connections errors (threshold)
• binary logging not enabled
• sync_binlog not set
• max_used_connections too high compared to max_connections (ratio over 85% utilization)
• query cache size too small: improper utilization
• query cache size too large: improper utilization
• memory usage over 85% of system ram
• table scans excessive
• tmp table to disk ratio too high
• innodb buffer too small
• innodb buffer too large (resources can be used elsewhere)
• key buffer too large (resources can be used elsewhere)
• key buffer too small
• sort buffer too small
• sort buffer too large (resources can be used elsewhere)
• join buffer too small
• join buffer too large (resources can be used elsewhere)
• open_files_limit too small compared to open_files usage ratio
• table locks too high
• table cache too small
• table cache too large (resources can be used elsewhere)
• thread cache too small
• thread cache too large (resources can be used elsewhere)
• binlog size too small
• excessive disk tmp table usage
• flush time not zero value
• indexes not being utilized properly
• innodb doublewrite buffer enabled
• innodb flush method not properly set
• innodb transaction isolation level not properly set for ACID
• innodb log wait time too high
• conncurrent insert not set correctly
• query cache not enabled
• table locks too high
• thread cache not enabled
• concurrent queries too high (threshold)
• binary logs not set to auto-purge
• binary logging not enabled
• slave not active if server is set to slave
• slave sql thread stopped
• slave io thread stopped
• slave behind master too long (threshold)
• slave not set as read-only
• slave relay logs not automatically purged
• account has global privs
• account set to old_password
• accounts able to be added with empty password
• account has grant option
• root can login remotely
• root has no password
• blank username detected
• test database exists
• usage user exists
• general query log enabled
• CPU usage over threshold
• Load Average over threshold

Graphs - default

• Query cache utilization, in/out hit ratio
• Temp tables usage
• Temp files usage
• Open tables usage
• Thread cached / created
• Connections
• Query rate
• Data size, Index size, overall size
• Uptime
• CPU usage
• I/O usage
• Load average
• Data transfer in/out
• Memory allocation
• Swap usage
• Slave delay (if configured as a slave)

As mentioned before, this is a OSS application that has no license or subscription fees and will be updated on a regular basis. It’s a mix of PHP for the web side and Perl for the system polling and reporting processes. The installer will be new, web based, and a simple process, much improved from the current method.Please add your comments now, as I am drawing up plans this week for version 2.