FrontPage |
UserPreferences |
The PEAK Developers' Center | FrontPage | RecentChanges | TitleIndex | WordIndex | SiteNavigation | HelpContents |
When beginning to explore PEAK, the best order in which to explore the modules is: binding, config, naming. These core modules provide the component-oriented framework upon which most other PEAK modules are built, and they will also be at the core of any application which uses PEAK.
The next layer to explore should probably be the runtime modules: ?running, commands, and logs. Combined with the previous core modules, the runtime modules provide most of the machinery needed for building a PEAK application.
The storage module provides numerous storage management features, including high level relational database connectivity, a general transaction framework with ACID assurance and two-phase commit, and a ?DataManager framework for high level object persistence to multiple storage media.
The model module provides a framework for implementing the ?DomainModel pattern, consisting of high level "business objects" isolated from storage concerns.
The events module provides an "event-driven" programming framework that supports ultralight "microthreads" implemented via generators. It can stand alone or can be used atop Twisted for a more intuitive approach to asynchronous programming.
Further modules to explore include the ?util, ?metamodels, and ?security modules. The ?web, ?net, and ?query are under development.
?PeakForTheImpatient (lranen)
To learn more about what a WikiWikiWeb is, read about WhyWikiWorks and the WikiNature. Also, consult the WikiWikiWebFaq.