cvsuser 03/12/03 08:17:42
Modified: App-Context/lib/App faq.pod
Log:
rough update
Revision Changes Path
1.3 +28 -27 p5ee/App-Context/lib/App/faq.pod
Index: faq.pod
===================================================================
RCS file: /cvs/public/p5ee/App-Context/lib/App/faq.pod,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -w -r1.2 -r1.3
--- faq.pod 1 Nov 2002 20:18:22 -0000 1.2
+++ faq.pod 3 Dec 2003 16:17:42 -0000 1.3
@@ -6,12 +6,13 @@
=head1 NAME
-App::faq - App Frequently Asked Questions
+App::faq - App-Context Frequently Asked Questions
=head1 INTRODUCTION
This is the FAQ for the
-App (Perl 5 Enterprise Environment).
+App-Context software framework
+(a variant of the Perl 5 Enterprise Environment).
You can find out more background to the project on the web.
http://www.officevision.com/pub/p5ee
@@ -19,7 +20,7 @@
=head1 GENERAL
-=head2 Why should I use App rather than J2EE or .NET?
+=head2 Why should I use App-Context rather than J2EE or .NET?
Perhaps it's because you prefer writing in Perl?
But besides that, there are other reasons.
@@ -60,20 +61,20 @@
a blueprint for large-scale development and deployment of
high-performance, high-availability systems (i.e. enterprise
systems) along with guides of discipline for coding and
-documentation. The App fills this gap.
+documentation. The App-Context framework fills this gap.
-So that's the explanation of "why App?"
+So that's the explanation of "why App-Context?"
-For an explanation of "why not App?" you might consider that it
+For an explanation of "why not App-Context?" you might consider that it
is still largely vaporware.
-=head2 How well does the App fit into a .NET technical strategy?
+=head2 How well does the App-Context fit into a .NET technical strategy?
-It may seem that App is most at home with the following technologies.
+It may seem that App-Context is most at home with the following technologies.
* Perl, Linux, Apache, CGI, and MySQL.
-However, the App abstracts much of the
+However, the App-Context framework abstracts much of the
runtime environment, so that it is just as easy to use:
* Perl, Windows NT, IIS, ISAPI, and SQLServer.
@@ -96,20 +97,20 @@
to run on the .NET CLR.
http://www.parrotcode.org/faq/
-=head2 What is the relation between App and mod_perl?
+=head2 What is the relation between App-Context and mod_perl?
The people who have been developing and working on mod_perl have done
an incredible service to Enterprise Perl in general, and therefore
-the App in particular. Other efforts that dramatically enhance
+the App-Context in particular. Other efforts that dramatically enhance
Enterprise Perl are SOAP projects, XML projects, DBD/DBI::*,
Templating projects, etc. These are all making dramatic contributions,
and they need not change anything they are doing in order to continue
to do so.
-On the contrary, the responsibility is on the designers of the App
+On the contrary, the responsibility is on the designers of the App-Context
to accommodate and incorporate these many enterprise-class technologies
-into an integrates whole. Browse the classes envisioned for App
-by App to see one way that these might fit together. Take
+into an integrates whole. Browse the classes envisioned for App-Context
+to see one way that these might fit together. Take
special note of the "Classes (Planned)" at the bottom of the
"All Classes" frame.
@@ -121,23 +122,23 @@
http://www.officevision.com/pub/p5ee/software/htdocs/Appx/Blue/Context.html
There is no need for the mod_perl project to explicitly
-integrate with App. However, in the spirit of community,
-as the App grows in its capabilities, I would imagine a
-natural cross-fertilization of ideas would occur so that if App needed
+integrate with App-Context. However, in the spirit of community,
+as the App-Context grows in its capabilities, I would imagine a
+natural cross-fertilization of ideas would occur so that if App-Context needed
any specific feature in mod_perl it would be implemented without
too much trouble.
-However, App reaches further than just running in a mod_perl Context.
-App is equipped with (when they are written, of course) a variety of
-Context classes which allow App software to run in many other Contexts
+However, App-Context reaches further than just running in a mod_perl Context.
+App-Context is equipped with (when they are written, of course) a variety of
+Context classes which allow App-Context software to run in many other Contexts
besides mod_perl.
-=head2 What does it mean for App to support Perl 5.5.3 if some of its components
require a higher version of Perl?
+=head2 What does it mean for App-Context to support Perl 5.5.3 if some of its
components require a higher version of Perl?
-The App (as envisioned in App) is like a software backplane
+The App-Context is like a software backplane
for many services required by an enterprise application. Into that
-backplane plug the App Services. There may be many implementations
-of each of the App Services, making for an almost limitless array
+backplane plug the App-Context Services. There may be many implementations
+of each of the App-Context Services, making for an almost limitless array
of possible combinations. (Hopefully, favorites will emerge.)
The Context is a Core Service, like Session and Config.
@@ -148,7 +149,7 @@
the implementer may choose to deploy the software, and the software
could reasonably run on all of them. The fact that (the envisioned)
App::Context::Modperl2 depends on 5.6.0 does not invalidate
-the fact that the App depends only on 5.5.3. Implementers who
+the fact that the App-Context depends only on 5.5.3. Implementers who
choose to deploy with Services that have higher Perl version
dependencies must of course satisfy those dependencies.
@@ -171,9 +172,9 @@
big budget projects with the latest new hardware. My experience
with customers who are large enterprises is that they have an
incredible mish-mash of systems and legacy environments. I envision
-that App software could be installed on every platform they own
+that App-Context software could be installed on every platform they own
(isn't Perl almost the most-ported language on the planet?).
-That is why I believe that App must support 5.5.3 (or perhaps
+That is why I believe that App-Context must support 5.5.3 (or perhaps
earlier, but I won't go there yet until I see a real need to
and understand exactly what I would be giving up).
