Webmachine gives you a place to define the representations and other Web-relevant properties of your application's resources -- with the emphasis that the first-class things on the Web are resources and that their essential properties of interaction are already quite well defined and usefully constrained.
ould call Webmachine a REST toolkit if you wanted, and I wo uldn't argue with you. However, even that doesn't tell you what exactly it does.
+You c call Webmachine a REST toolkit if you , and I won't argue with you. However, even that doesn't tell you what exactly it does.
It is an application layer that adds HTTP semantic awareness on top of the excellent bit-pushing and HTTP syntax-management provided by mochiweb.
The very first implementation of Webmachine was inspired in large part by version 1 of Alan Dean's HTTP flow diagram. I subsequently worked with Alan to improve the diagram as we developed Webmachine. Webmachine's request handling engine reflects the result of that collaboration explicitly.
write some more content here