Apache::AxKit::Language::XSP Apache::AxKit::Language::XSP is a Perl module with eXtensible Server Pages.
Download

Apache::AxKit::Language::XSP Ranking & Summary

Apache::AxKit::Language::XSP Tags

server Perl module extensible eXtensible Server Pages Apache AxKit

Apache::AxKit::Language::XSP Description

Apache::AxKit::Language::XSP is a Perl module with eXtensible Server Pages. Apache::AxKit::Language::XSP is a Perl module with eXtensible Server Pages.SYNOPSIS < xsp:page xmlns:xsp="http://apache.org/xsp/core/v1" > < xsp:structure > < xsp:import >Time::Object< /xsp:import > < /xsp:structure > < page > < title >XSP Test< /title > < para > Hello World! < /para > < para > Good < xsp:logic > if (localtime->hour >= 12) { < xsp:content >Afternoon< /xsp:content > } else { < xsp:content >Morning< /xsp:content > } < /xsp:logic > < /para > < /page > < /xsp:page >XSP implements a tag-based dynamic language that allows you to develop your own tags, examples include sendmail and sql taglibs. It is AxKit's way of providing an environment for dynamic pages. XSP is originally part of the Apache Cocoon project, and so you will see some Apache namespaces used in XSP.Also, use only one XSP processor in a pipeline. XSP is powerful enough that you should only need one stage, and this implementation allows only one stage. If you have two XSP processors, perhaps in a pipeline that looks like: ... => XSP => XSLT => XSLT => XSP => ...it is pretty likely that the functionality of the intermediate XSLT stages can be factored in to either upstream or downstream XSLT: ... => XSLT => XSP => XSLT => ...This design is likely to lead to a clearer and more maintainable implementation, if only because generating code, especially embedded Perl code, in one XSP processor and consuming it in another is often confusing and even more often a symptom of misdesign.Likewise, you may want to lean towards using Perl taglib modules instead of upstream XSLT "LogicSheets". Upstream XSLT LogicSheets work fine, mind you, but using Perl taglib modules results in a simpler pipeline, simpler configuration (just load the taglib modules in httpd.conf, no need to have the correct LogicSheet XSLT page included whereever you need that taglib), a more flexible coding environment, the ability to pretest your taglibs before installing them on a server, and better isolation of interface (the taglib API) and implementation (the Perl module behind it). LogicSheets work, and can be useful, but are often the long way home. That said, people used to the Cocoon environment may prefer them. Requirements: · Perl

Apache::AxKit::Language::XSP Related Software