Manage an HTTP Server Using RESTful Interfaces and Project Zero

WS-* users and REST users have an ongoing debate over which technique
is most appropriate for which problem sets, with WS-* users often
claiming that more complex, enterprise-level problems cannot be solved
RESTfully. This article puts that theory to the test by trying to
create a RESTful solution for a problem area that is not often
discussed by REST users: systems management. The article shows how to
make a Zero-based RESTful interface for httpd that is as functionally
complete, comparable to an Apache Muse-based WS-* version. The
combination of Groovy scripts and RESTdoc comments provides the same
features and behavior as we had with Java classes and WSDL and
demonstrates that REST can handle the tasks that are thought to be
"too complicated" for HTTP alone. The REST and WS-* solutions each
have their pros and cons, and which one you favor may change from
project to project. The article not about enumerating the pros and
cons of WS-* technology versus REST-oriented technology, and it is
not out to select a "winner." The goal of the article is to demonstrate
whether or not REST and Web 2.0 development techniques provide a
productive alternative for systems management projects and hopefully
give developers some additional choices. WS-* users and REST users
have an ongoing debate over which technique is most appropriate for
which problem sets, with WS-* users often claiming that more complex,
enterprise-level problems cannot be solved RESTfully.