For the majority that doesn't know what's this all about: phpSATk is intended to be a Framework (and some kind of application server) helping network/system administrators to write small (or even larger) management applications. In my opinion using standard techniques this is a very unproductive task making you spend a huge amount of time on things like form processing (if done securely and user friendly) which do not add to the application's core functionality. phpSATk tries to help you with that. Also it tries to force and support you in making your applications extensible and interoperable. (more to come...)
There are not yet any real application built based on phpSATk and you're also not adviced to do so, because the API is not stable yet.
Features include (yet) ...
- Module management which provides depency resolving and "virtual" modules
- XML based configuration
- Caching (for acceptable speed)
- Multiple input methods: Plain HTTP (Browser request), various Webservice formats (only XMLRPC atm, but more to come), CLI Requests
- Extensible application controller for dispatching calls
- Modular error management (including per request type outputs)
- Modules authentication system:
- Frontends include HTTP-Auth, session based authentication, session-independ token-based authentication.
- Backend include RDBMS-storage, LDAP-storage, LDAP-Auth+RDBMS-storage
- Modular authorization subsystem (role based) allowing you to define new authentication resources for you application (well, it's not perfect yet)
- Form generation (requires some modifications to keep up with view generation mentioned below)
- Object oriented LDAP interface
- No extra layer for RDBMS access (PDO is quite nice I think)
- Socket/HTTP/XMLRPC-Clients
- ZPT-style TAL Templates (using PHPTAL)
- eXtensible Data Objects: Aggregateable data access object
- XDO helpers for RDBMS data sources and LDAP data sources
- DataSets for XDOs: Collections of XDOs
- View generation for XDOs and DataSets
