This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Date: Mon, 2 Oct 2000 19:29:56 +0100 (BST) From: Matt Sergeant <matt@sergeant.org> To: AxKit Users Mailing List <axkit-users@axkit.org> Subject: [ANNOUNCE] AxKit 1.0 I've finally managed to put AxKit 1.0 out, after a long run-up to the 1.0 release. There are a couple of known issues with XSP and a couple of other potential bugs still standing, but the API is now stable, and we can add further enhancements as "bug fixes" now. Despite these minor bugs, AxKit has proved to be very stable for production use, with no noticable memory leakage over time. Specific new features of 1.0 include: - Config directives now all documented in perldoc AxKit - XPathScript now much calls apply_templates if there is no output - New Filter provider allows AxKit to work with the output from Mason, Apache::ASP, or RegistryFilter scripts. - Improved error handling and reporting Please visit http://axkit.org/ for more information. For those who don't know, details of what AxKit is are below: AxKit is an XML Application Server for Apache. It provides on-the-fly conversion from XML to any format, such as HTML, WAP or text using either W3C standard techniques, or flexible custom code. AxKit also uses a built-in Perl interpreter to provide some amazingly powerful techniques for XML transformation. The emphasis with AxKit is on separation of content from presentation. The pipelining technique that AxKit uses allows content to be converted to a presentable format in stages, allowing certain platforms to see data differently to others. AxKit allows web designers to focus on web site design, content developers to work on a purely content basis, and webmasters to focus on their core competencies. AxKit is based on components that are replaceable. This allows the web site developer to create a completely custom XML Application Server based around the AxKit API. AxKit can either automatically provide caching facilities, or you can create your own cache handler, so that XML transformations (which can be time consuming) only happen when required. The toolkit also provides ability to build component based web sites, and dynamic content. Database integration is fully supported, allowing either deliver of XML from a database, or XML generation from a database query. Dynamic web components can be built using the Perl language, making the possibilities as infinite as CGI scripts, without the potential mess that CGI programming can cause. -- <Matt/> Fastnet Software Ltd. High Performance Web Specialists Providing mod_perl, XML, Sybase and Oracle solutions Email for training and consultancy availability. http://sergeant.org | AxKit: http://axkit.org