| HAPI |
Quick Start: |
Jump straight to the HAPI applications. |
Summary: |
|
|
From the spec: The goal [of HAPI] is to create a framework that will allow applications to work together as modules. The framework should be very lightweight, so that it's not a burden to develop to. (i.e. making compliant applications is as easy as possible) It should be as transperent as possible, allowing the applications to stand alone or to be installed next to other compliant modules as parts of a larger application. Common obstacles to these goals that this version of the spec address are: - Each application has its own set of administrators and users. - Each application has its own incompatible login and session management system. - Each application has its own administrative front door, centralizing control is difficult - Applications may name database tables in a way that conflict with each other. | |
Information |
The HAPI Spec The HAPI table schema |
Tools |
IMPORTANT! My prototyping for the HAPI specification has been done in PHP. It's critical to distinguish between my PHP implementations and the cross platform nature of the HAPI specification. HAPI authentication for PHP HAPI auth test (source) db classes dbPop classes Password generator |
Applications |
HAPI compliant applications: - classAd - mailList - storyMaker - online store Browse |