|
A key philosophy of Nitro is that it does not dictate how a web application should be structured. One can use templates with embedded code, as is typical with PHP or ASP, or one can model-view-controller approach, as found in for instance Ruby on Rails, or expand even further with a custom architectural pattern. Nitro features support for Ajax, XML, web services and syndication while staying standards compliant. One of its key distinctions from other similar frameworks is its use of Og as the object-relational database mapping layer. Og can create database tables based on Ruby classes, or it can be easily adapted to use an existing database schema. |