Yote is a web application server, a set of perl libraries and, a set of javascript libraries. It is designed for the rapid development of web applications. This website is run from a yote server as are all the apps that appear on this site.

Yote objects are container objects organized in a tree that are automatically saved by the server and require no table definitions. A master process runs yote methods and is the only process that can touch the backend datastore (currently SQLite, but drivers can be made for other data stores).

Yote is just venturing as an alpha release. This means that, while there are test programs to make sure it is doing its job, there are likely bugs that the test program does not yet test for. It means that not all features have been created even if they are planned.

Yote is for the Impatient; those people who want to code the business logic and object to object relationships without having to muck about writing table schemas.
Yote is for someone who wants to put a prototype of a web application together in short order.

• Objects defined on the server side have automatically created proxies on the client side.
• Objects on the client side are transparently updated when changed on the server side
• Any key value pair can be attached to any Yote object as long as the key is a string and the value is a string, number, array, hash or Yote object.
• Yote objects are lazilly loaded and active in memory while being used.
• The key value pairs attached to any Yote object are automatically saved.
• All active Yote objects can trace a reference back to the root Yote object