Why do I like this blog so much?
I feel free here.
By yesterday I'll need to have a secure, language neutral, fully templated and administratable php objectbase that speaks http and rfc822. Efficient enough for message threading. With queues.
Intelligent request, auth, db, language, object, action and template classes form the framework. A number of secondary classes fill out the suite: cache, queue, rfc822, subscription, filter, subrequest.
Actions can make subrequests to get external data from webservices. Subrequests can trigger a wait loop in the main requst. Objects will also make http subrequests if necessary to discover content.
Action scripts can call filters, chains of php scripts that act on a common stdin, stdout, and stderror.
Templates are objects that execute php scripts in output buffers, each with a local scope. The template itself and helper methods are available to template writers using $this.
You can learn alot by tacking ?debug=1 on the end of the request url.
Well, it should be pointed out that I have all of this stuff scattered around in 4 different projects, and I desperately want to bring them together under a sinle open license. We'll see if I can swing that.
The open library has request, db, flat objects, actions, and templates. No auth. No language.
The not-yet-open library has 3d objects (almost), auth, and language. And a capable imageserver.
Paxi has subrequests.
Clew has subscriptions, and, sans filters, mail handling. Clew mails itself a copy of every new object.
Cache, queue and filter are mia. But it's all good.
I feel free here.
By yesterday I'll need to have a secure, language neutral, fully templated and administratable php objectbase that speaks http and rfc822. Efficient enough for message threading. With queues.
Intelligent request, auth, db, language, object, action and template classes form the framework. A number of secondary classes fill out the suite: cache, queue, rfc822, subscription, filter, subrequest.
Actions can make subrequests to get external data from webservices. Subrequests can trigger a wait loop in the main requst. Objects will also make http subrequests if necessary to discover content.
Action scripts can call filters, chains of php scripts that act on a common stdin, stdout, and stderror.
Templates are objects that execute php scripts in output buffers, each with a local scope. The template itself and helper methods are available to template writers using $this.
You can learn alot by tacking ?debug=1 on the end of the request url.
Well, it should be pointed out that I have all of this stuff scattered around in 4 different projects, and I desperately want to bring them together under a sinle open license. We'll see if I can swing that.
The open library has request, db, flat objects, actions, and templates. No auth. No language.
The not-yet-open library has 3d objects (almost), auth, and language. And a capable imageserver.
Paxi has subrequests.
Clew has subscriptions, and, sans filters, mail handling. Clew mails itself a copy of every new object.
Cache, queue and filter are mia. But it's all good.
