Detailed explanation of XML and sample code for modern CGI applications

Introduction

The popularity of Perl is directly related to the vigorous development of the Internet. Perl's powerful functions and easy expansion make it the most natural choice for developing CGI applications, and it has quickly become the preferred language for CGI scripts. CGI itself is not perfect. But thanks to the favor of many developers, CGI is still widely used today and shows no signs of "retiring" in the near future.

A typical CGI::XMLApplication script consists of three parts: a small executable script that provides access support to the application, a logic module that implements various manager methods, and a logic module that implements various manager methods. ##There may be one or more XSLT style sheets. XSLT style sheets can convert the results returned by the module into a format that the browser can display to the user. Below we briefly introduce the application of CGI::XMLApplication through examples.

Example 1: CGI XSLT Gateway

CGI::XMLApplication assumes that the designers and developers involved in a project separate the logic and presentation of the application using XSLT stylesheets to make this separation apparent Very direct and will not have any impact on the project. Developers only need to be able to make setStylesheet return the location of the XSLT style sheet that matches the current application state. The conversion of the DOM tree created by the application, the transmission of XSLT parameters to the conversion engine, and the transmission of converted content to the browser are all transparent to users.

To highlight this separation, our first example is not a web application in the traditional sense, but a generic XSLT gateway that can be added to the server's cgi-bin to convert the entire XML content The directory tree is converted into a format that conforms to the requesting browser, and all this is transparent to users, stylesheets, and document authors.

The first step is to establish a CGI script that connects the client's request and application. We want to make XML documents easily browseable via URLs and make creating hyperlinks between these documents intuitive. Therefore, we will create a CGI script without the extension so that as a node in the URL path, everything to the right of the node will be interpreted within a virtual document environment containing XML content. In this case, we call CGI a style sheet selector.

use strict;
use lib '/path/to/secure/webapp/libs';
use XSLGateway;
use CGI qw(:standard);my $q = CGI->new();
my %context = ();
my $gateway_name = 'stylechooser';

After loading the appropriate modules and setting some

that are valid throughout the script, we start adding some fields to the %context that is passed to the class that handles the application logic . In this application, we only pass the requested URL (REQUEST entry) to the right of the path to the script file and the STYLE key containing the data stored in the query parameter style.

$context{REQUEST} = $q->url(-path => 1);
$context{REQUEST} =~ s/^$gateway_name/?//;
$context{REQUEST} ||= 'index.xml';
$context{STYLE} = $q->param ('style') if $q->param('style');

my $app = XSLGateway->new();
$app->run(%context);

The CGI script is complete. Next we create the XSLGateway module that does most of the work:

package XSLGateway;
use strict;
use vars qw(@ISA);
use CGI::XMLApplication;
use XML::LibXML;
@ISA = qw(CGI::XMLApplication);

As I mentioned in the introduction, CGI::XMLApplication works via

calls: a given in the application class The execution of a certain method depends on the input of a specified field (usually the name of the button used to submit the form.), and two calling methods must be executed: selectStylesheet and requestDOM method. selectStylesheet returns the full

path to the relevant XSLT style sheet. For simplicity, we assume that the stylesheet will be kept in a single directory. We can provide other style sheets through the $context-> {STYLE} field to increase the flexibility of the system.

sub selectStylesheet {
my $self = shift;
my $context = shift;
my $style = $context->{STYLE} || 'default';
my $style_path = '/opt/www/htdocs/stylesheets/';
return $style_path . $style . '.xsl';
}

of the XML document being transferred. Since our gateway only works with static files, we need to use XML::LibXML to parse the document and return the result tree.

sub requestDOM {
my $self = shift;
my $context = shift;
my $xml_file = $context->{REQUEST} || 'index.xml';
my $doc_path = '/opt/www/htdocs/xmldocs/';
my $requested_doc = $doc_path . $xml_file;
my $parser = XML::LibXML->new;
my $doc = $parser->parse_file($requested_doc);
return $doc;
}

如果需要，我们可以扩充这一基本的框架，例如，可以 在样式表选择CGI脚本程序添加一些查找组件，选择合适的样式表，可以设置或读 取HTTP cookies，对网站进行修饰。

例2：一个简单的购物系统

在 该例子中，我们将使用CGI::XMLApplication创建一个简化的Web应用程序，购物 系统。

与上个例子相同，这个应用程序中与CGI-BIN有关的部分仍然非常 地少。我们所需要作的只不过是初始化CustomerOrder应用类并调用它的run()方 法。这次，我们将CGI.pm中Vars作为%context的PARAMS域：

use strict;
use CGI qw(:standard);
use lib '/path/to/secure/webapp/libs';
use CustomerOrder;
my $q = CGI->new();
my %context = ();
$context{PARAMS} = $q- >Vars;
my $app = CustomerOrder->new();
$app->run(% context);

在这个例子中，我们假定该应用中的产品信息存储在关 系数据库中，产品清单不是太长，使我们在应用中不会出现多屏才能显示相关信 息的麻烦：用户输入订购的产品数量的主要数据输入屏，显示订购单内容和所选 物品总价格的确认屏，显示订单已经处理的提示。为了简单起见，我们在这里没 有涉及送货和财务数据的输入等问题。

package CustomerOrder;
use strict;
use vars qw(@ISA);
use CGI::XMLApplication;
use XML::LibXML::SAX::Builder;
use XML::Generator::DBI;
use DBI;
@ISA = qw (CGI::XMLApplication);

在加载必要的模块和定义从 CGI::XMLAplication中继承的类后，我们开始创建应用中与各种状态有关的事件 调用。首先，我们必须通过创建registerEvents()方法注册这些事件。在本例中 ，我们将注册order_confirm 和order_send方法，这二个方法设置%context中的 SCREENSTYLE域。稍后，我们将利用该属性定义在显示客户端的数据时应该使用三 个XSLT样式表中的哪一个。

需要注意的是，这些事件将被映射到实现它们 的实际的子程序中，子程序的命名规则是event_<事件名>，例如， order_confim事件是由event_order_confim执行的。另外，还需要注意的是，各 种事件的选择是由CGI::XMLApplication根据其查找一个与注册事件同名的表格参 数的能力进行的。例如，要执行order_confirm事件，表格组件中必须包含一个提 交非空值的名字为order_confirm的表格域。

# 事件的注册和事件调用

sub registerEvents {
return qw( order_confirm order_send );
}
sub event_order_confirm {
my ($self, $context) = @_;
$context->{SCREENSTYLE} = 'order_confirm.xsl';
}
sub event_order_send {
my ($self, $context) = @_;
$context->{SCREENSTYLE} = 'order_send.xsl';
}

如果没有请求执行其他的事 件，则缺省地执行event_default。在本例中，我们只使用它将SCREENSTYLE域设 定为一个合适的值。

sub event_default {
my ($self, $context) = @_;
$context->{SCREENSTYLE} = 'order_default.xsl';
}

每次请求都会执行 event_init方法，而且总是在其他方法之前执行它，这使得它非常适合对应用中 被其他事件使用的部分进行初始化。在本例中，我们使用它返回利用 fetch_recordset()方法从数据库中获取的产品信息的、最初的DOM树。

sub event_init {
my ($self, $context) = @_;
$context->{DOMTREE} = $self->fetch_recordset();
}

state-handler方法完成后，我们需要执行必需的 selectStylesheet和requestDOM方法。

与在第一个例子中一样，我们假设 所有的应用的样式表都存储在服务器上相同的目录中。我们所需要作的是返回 $context->{SCREENSTYLE}的值所指定的路线，并添加到末尾。

# app config and helpers
sub selectStylesheet {
my ($self, $context) = @_;
my $style = $context-> {SCREENSTYLE};
my $style_path = '/opt/www/htdocs/stylesheets/cart/';
return $style_path . $style;
}

在研究requestDOM处理程序之前，我们先来详细 地研究fetch_recordset helper方法。

需要记住的是，我们要做的工作是 从一个关系数据库中选择所订购产品的有关信息，但传递给XSLT处理器的数据必 须是DOM树。在本例中，我们不通过编程的方法，而是利用XML::Generator::DBI ，它能够从执行SQL SELECT语句得到的数据中生成SAX数据。创建要求的DOM树就 是建立XML::LibXML::SAX::Builder（它从SAX事件中创建XML::LibXML DOM树）的 实例。

sub fetch_recordset {
my $self = shift;
my $sql = 'select id, name, price from products';
my $dbh = DBI->connect('dbi:Oracle:webclients',
'chico',
'swordfish')
|| die "database connection couldn't
be initialized: $DBI::errstr n";
my $builder = XML::LibXML::SAX::Builder->new();
my $gen = XML::Generator::DBI->new(Handler => $builder,
dbh => $dbh,
RootElement => 'document',
QueryElement => 'productlist',
RowElement => 'product');
my $dom = $gen->execute($sql) || die "Error Building DOM Treen";
return $dom;}

fetch_recordset方法完成了另一项很重要的任务，但它返回的 DOM树只包含我们想向客户发送信息的一部分，我们还必须获取用户输入的产品数 量，另外，还需要提供一个订购产品的总计。

sub requestDOM {
my ($self, $context) = @_;
my $root = $context-> {DOMTREE}->getDocumentElement();
my $grand_total = '0';

为了将当前的订货数量作为更大的文档的一部分， 我们将遍历所有的产品元素，并在每行中添加和子元素。的值可以从$context- >{PARAMS}域获得。

foreach my $row ($root->findnodes ('/document/productlist/product')) {
my $id = $row- >findvalue('id');
my $cost = $row->findvalue ('price');
my $quantity = $context->{PARAMS}->{$id} || '0';
my $item_total = $quantity * $cost;
$grand_total += $item_total;
# add the order quantity and item totals to the tree.
$row->appendTextChild('quantity', $quantity);
$row->appendTextChild('item-total', $item_total);
}

最后，我们将增加一些有关订单的元信息 ，方法是在具有元素的根元素中添加一个元素，该元素中包含有当前所选货物的 总价值。

$grand_total ||= '0.00';
my $info = XML::LibXML::Element->new('instance-info');
$info- >appendTextChild('order-total', $grand_total);
$root- >appendChild($info);
return $context->{DOMTREE};
}

细心的读者可能已经注意到，我们这个非常简单的应用程序在 order_send方法中没有作任何实际的事。决定如何处理这些数据是产品订购应用 程序中与具体的购物网站最有关的部分。

结束语

CGI::XMLApplication在CGI脚本程序的编程中提供了一种清晰的、模块化 的隔离系统的内容和表示的方法，单就这一点，就值得我们对它进行一番研究。 此外，它还可以使我们避免纠缠于一些细节问题，而集中精力解决主要的问题。

【相关推荐】

1. Detailed explanation of the example code of cgi writing data to text or database

2. Sharing an example tutorial on running Python scripts using CGI on IIS

3. Using CGI module to create a simple web page tutorial example

4. Share an example tutorial of Python CGI programming

5 . What is CGI? Detailed introduction to Python CGI programming

6. FastCGI process unexpectedly exited causing 500 error

The above is the detailed content of Detailed explanation of XML and sample code for modern CGI applications. For more information, please follow other related articles on the PHP Chinese website!