FlightFeather's goal is 'social networking for everyone'.
FlightFeather's design has reflected its goal from the very beginning. Whenever the system's state changes, FlightFeather generates static HTML pages. Pure read operations -- usually about 90% of the total -- do not require the application to run at all.
FlightFeather's sister project -- Flightdeck-UI -- likewise uses this Relative Static technique (i.e. the application-generated dynamic data appears as static pages to the Web server). The author also presented these concepts at LinuxWorld San Francisco 2006.
FlightFeather does not use a separate SQL database. In-memory data structures and Berkeley DB augment the static HTML pages to maintain a consistent state. The overall approach may be termed LAP -- a variation on the highly effective LAMP platform. LAMP stands for Linux, Apache, MySQL and Perl/Python/PHP (although there can be further variations).
FlightFeather drops the "M" from this formula, in favor of capturing as many system state changes as possible into complete, static HTML documents. Apache can then serve these documents by itself, while FlightFeather waits in the background.
What's New in This Release:
· This release modifies the way the FlightFeather server loads the configuration, protocol, session, and storage modules on startup.
· The actual loading process now takes place after all options have been parsed.
· If the "-c" or "--command" option is present, the server does not import these modules at all, since they are not required.
· The new implementation also fixes a bug that caused the test versions of the above modules to always load, in addition to any modules specified on the command line.