To understand Tonic, you need to get the Web, so forget everything you know for a minute and think about how the Web really works, it's not about HTML pages, it's about resources:
- Everything useful is a resource, not a file, not a script, a resource, an abstract concept of something useful that the client wants to grab hold of. script, a resource, an abstract concept of something useful that the client wants to grab hold of.
- Resources are located by s, URLs are cheap and form the universal addressing system of the Web. s, URLs are cheap and form the universal addressing system of the Web.
- Clients can issue a standard number of HTTP methods upon an infinite number of resources and receive something useful in return.
- Representations of resources are sent back to the client, a representation is just a way of turning the abstract concept of a resource into something more concrete, like a HTML page or a XML file. One resource can have many different representations.
Tonic works exclusively with resources, a resource is simply a piece of data with some metadata accessable by a URL using HTTP methods. Everything within a Tonic system is a resource and so can be handled via the standard HTTP interface.
When modelling your problem domain within a Tonic system, every domain object is a resource or a collection of resources.
· PHP 5.3 or higher