> Another thing - a while back Michael Graham announced a pre-release of > CGI::Application::Framework > (http://www.mail-archive.com/[email protected]/msg03533.html) I don't > know where it's at, but if it's likely to be prod quality when you write > your book, then it may be worthwhile covering. Although many C::A developers > will have their own preferred framework, I certainly could have used > something like C::A::F when starting out with C::A - it would have saved me > from going down a few blind alleys.
The CAF is quite useable now, but the API is not quite in its "final" state yet. The two main API changes on the horizon are to switch our built-in session system over to CAP::Session and to switch our own authentication/login system to CAP::Auth. Hopefully both of these changes will happen sometime in September. After that, we've still got lots of cool features planned, but those will mostly be additions, not changes, and won't require that authors rewrite their apps each time they upgrade the Framework. Interestingly, when we pass that milestone, the CAF codebase will consist almost entirely of CGI::Application plugins. I think its place within the CGI::Application community at that point will be to serve as one possible answer to the questions of "how the heck do I use all these plugins?" and "where do I put all my modules, templates, and config files?". Michael --- Michael Graham <[EMAIL PROTECTED]> --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
