cvsuser 02/06/01 19:29:52
Modified: P5EEx/Blue/P5EEx/Blue devguide.pod
Log:
cgi program is now p5x instead of p5ee
Revision Changes Path
1.7 +16 -16 p5ee/P5EEx/Blue/P5EEx/Blue/devguide.pod
Index: devguide.pod
===================================================================
RCS file: /cvs/public/p5ee/P5EEx/Blue/P5EEx/Blue/devguide.pod,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -w -r1.6 -r1.7
--- devguide.pod 10 May 2002 21:07:35 -0000 1.6
+++ devguide.pod 2 Jun 2002 02:29:52 -0000 1.7
@@ -73,17 +73,17 @@
and the need to properly shut down all resources after using
them or in case of user abort.
-=head2 cgi-bin/p5ee and the Initialization Config File
+=head2 cgi-bin/p5x and the Initialization Config File
All usage of P5EE from the web can be driven through the CGI program,
-"cgi-bin/p5ee". (Actually, depending on the settings in the Initialization
-Config File, the "p5ee" program might not be a CGI program at all.)
-The p5ee program should be installed at a location which is executable
+"cgi-bin/p5x". (Actually, depending on the settings in the Initialization
+Config File, the "p5x" program might not be a CGI program at all.)
+The p5x program should be installed at a location which is executable
as a CGI program such as the following.
- http://www.officevision.com/cgi-bin/pub/p5ee/p5ee
+ http://www.officevision.com/cgi-bin/pub/p5ee/p5x
-The "p5ee" progam runs with the "-wT" switches turned on for maximum
+The "p5x" progam runs with the "-wT" switches turned on for maximum
safety, security, and enforcement of programming rigor.
Then a BEGIN block is executed to read the Initialization Config File
@@ -97,12 +97,12 @@
First, the PATH_INFO is checked and a corresponding .conf file is opened.
Thus, the following URL
- http://www.officevision.com/cgi-bin/pub/p5ee/p5ee/ecommerce/shop
+ http://www.officevision.com/cgi-bin/pub/p5ee/p5x/ecommerce/shop
-would open "ecommerce_shop.conf" in the directory of the "p5ee" program.
+would open "ecommerce_shop.conf" in the directory of the "p5x" program.
If it is not found, "$0.conf" is opened. That would be "p5ee.conf"
-in this case. However, you can see that this allows for the "p5ee"
+in this case. However, you can see that this allows for the "p5x"
program to be renamed, and (according to its configuration) it will
behave like a completely different application.
@@ -129,7 +129,7 @@
debugmode = record
showsession = 1
gzip = 1
- configFile = p5ee.pl
+ configFile = app.pl
The meanings of these variables are:
@@ -161,7 +161,7 @@
the Initialization Config File. The CGI environment never passes options
to the program in this way (with a preceding dash), so this is mainly
useful for debugging at the command line
-(i.e. "p5ee -debugmode=replay -debug=1 -gzip=0").
+(i.e. "p5x -debugmode=replay -debug=1 -gzip=0").
=head2 use P5EEx::Blue::P5EE
@@ -187,9 +187,9 @@
P5EEx::Blue::Exception::Messaging
P5EEx::Blue::Exception::LogChannel
-=head2 cgi-bin/p5ee and bootstrapping the environment
+=head2 cgi-bin/p5x and bootstrapping the environment
-The "p5ee" program then executes the following line.
+The "p5x" program then executes the following line.
my $context = P5EEx::Blue::P5EE->context(\%main::conf);
@@ -207,7 +207,7 @@
=head2 P5EEx::Blue::P5EE->context()
If the "contextClass" variable is in the argument hash, it is used.
-Otherwise, if the "p5ee" program is running in the CGI context
+Otherwise, if the "p5x" program is running in the CGI context
(HTTP_USER_AGENT environment variable is set) or at the
command line, the P5EEx::Blue::Context::CGI class
will be assumed.
@@ -332,9 +332,9 @@
This state is stored in $session->{state} and the session
cache is initialized to an empty hashref.
-=head2 cgi-bin/p5ee and dispatching events
+=head2 cgi-bin/p5x and dispatching events
-The "p5ee" program finally executes the following line.
+The "p5x" program finally executes the following line.
$context->dispatch_events();
