[Openinteract-commits] CVS: OpenInteract2/doc/Manual Intro.pod,1.13,1.14

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Update of /cvsroot/openinteract/OpenInteract2/doc/Manual
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28785/doc/Manual

Modified Files:
	Intro.pod 
Log Message:
small updates

Index: Intro.pod
===================================================================
RCS file: /cvsroot/openinteract/OpenInteract2/doc/Manual/Intro.pod,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -d -r1.13 -r1.14
*** Intro.pod	30 Nov 2004 00:18:47 -0000	1.13
--- Intro.pod	17 Mar 2005 02:30:34 -0000	1.14
***************
*** 65,69 ****

  For more information about these concepts see
! L<OpenInteract2::Manual::Architecture|OpenInteract2::Manual::Architecture>.

  =head2 Context
--- 65,69 ----

  For more information about these concepts see
! L<OpenInteract2::Manual::Architecture>.

  =head2 Context
***************
*** 71,77 ****
  Holds all application configuration information and provides a central
  lookup mechanism. This is a singleton (there's only one in the system
! at any time) and can be imported from the
! L<OpenInteract2::Context|OpenInteract2::Context> class since it's used
! fairly often.

  =head2 Adapter
--- 71,76 ----
  Holds all application configuration information and provides a central
  lookup mechanism. This is a singleton (there's only one in the system
! at any time) and can be imported from the L<OpenInteract2::Context>
! class since it's used fairly often.

  =head2 Adapter
***************
*** 81,102 ****
  translates parameters from the user, information about the request
  (hostname, URL, referer, cookies, etc.) and other data into the
! relevant L<OpenInteract2::Request|OpenInteract2::Request> subclass.

  Once the OpenInteract cycle is complete it translates OpenInteract
  data (content, headers, etc.) into a response to send back to the user
! via the relevant L<OpenInteract2::Response|OpenInteract2::Response>
! subclass. For an example see
! L<Apache::OpenInteract2|Apache::OpenInteract2>.

  =head2 Controller

  Once the adapter has created the request and response it hands off the
! processing to the
! L<OpenInteract2::Controller|OpenInteract2::Controller> object. This
! reads the URL and creates the relevant action object that will
! generate the content. It knows which action object to create through a
! URL-to-action mapping created at server startup. The controller places
! the generated content in a larger scope so you can control common
! graphical elements (sidebars, menus, etc.) from one place.

  =head2 Action
--- 80,100 ----
  translates parameters from the user, information about the request
  (hostname, URL, referer, cookies, etc.) and other data into the
! relevant L<OpenInteract2::Request> subclass.

  Once the OpenInteract cycle is complete it translates OpenInteract
  data (content, headers, etc.) into a response to send back to the user
! via the relevant L<OpenInteract2::Response> subclass. For an example
! see L<Apache::OpenInteract2>.

  =head2 Controller

  Once the adapter has created the request and response it hands off the
! processing to the L<OpenInteract2::Controller> object. This reads the
! URL and asks a set of small objects called action resolvers to create
! an B<Action> from the URL. Once that action is created it executes the
! action which generates the primary content for the request. The
! controller places that content in a larger content scope so you can
! control common graphical elements (sidebars, menus, etc.) from one
! place.

  =head2 Action
***************
*** 104,113 ****
  Actions are the core of OpenInteract2. Each action provides a discrete
  set of functionality. What "discrete set" means is up to the
! developer, but typically this is a set of SCRUD (Search - CReate -
! Update - Delete) operations on a class of objects.

  Each action is represented by zero or more URLs, and each operation is
! specified by a task referenced in that URL. So if I created a 'news'
! action my URLs might look like:

   /news/search/
--- 102,111 ----
  Actions are the core of OpenInteract2. Each action provides a discrete
  set of functionality. What "discrete set" means is up to the
! developer, but typically this is a set of CRUDS (Create - Remove -
! Update - Display - Search) operations on a class of objects.

  Each action is represented by zero or more URLs, and each operation is
! typically specified by a B<task> referenced in that URL. So if I
! created a 'news' action my URLs might look like:

   /news/search/
***************
*** 117,123 ****

  Every task returns some sort of content, generally by passing data to
! a Content Generator which marries it with a template. See
! L<OpenInteract2::Action|OpenInteract2::Action> for much more
! information.

  =head2 Content Generator
--- 115,120 ----

  Every task returns some sort of content, generally by passing data to
! a B<Content Generator> which marries it with a template. See
! L<OpenInteract2::Action> for much more information.

  =head2 Content Generator
***************
*** 127,133 ****
  data off to a content generator. A content generator is a wrapper
  around some sort of templating system, such as the L<Template
! Toolkit|Template>, L<HTML::Template|HTML::Template> or
! L<Text::Template|Text::Template> or even your own homegrown
! system. (Admit it, you've written your own.)

  Each action is associated with a content generator. And you can even
--- 124,129 ----
  data off to a content generator. A content generator is a wrapper
  around some sort of templating system, such as the L<Template
! Toolkit|Template>, L<HTML::Template> or L<Text::Template> or even your
! own homegrown system. (Admit it, you've written your own.)

  Each action is associated with a content generator. And you can even
***************
*** 139,146 ****
  These are the major configuration files at the server level. Each
  package has its own configuration files -- see
! L<OpenInteract2::Manual::Packages|OpenInteract2::Manual::Packages> for
! more information about packages, and
! L<OpenInteract2::Manual::QuickStart|OpenInteract2::Manual::QuickStart>
! for how to modify some of these files to get a server started quickly.

  B<server configuration> - C<conf/server.ini>
--- 135,141 ----
  These are the major configuration files at the server level. Each
  package has its own configuration files -- see
! L<OpenInteract2::Manual::Packages> for more information about
! packages, and L<OpenInteract2::Manual::QuickStart> for how to modify
! some of these files to get a server started quickly.

  B<server configuration> - C<conf/server.ini>
***************
*** 158,164 ****
  determine the logging level for the whole server or discrete parts of
  it, which logfiles get written, when/if they're rolled over, etc. See
! L<OpenInteract2::Manual::Logging|OpenInteract2::Manual::Logging> for a
! quick intro to logging and read up about
! L<Log::Log4perl|Log::Log4perl> for details.

  B<interface configuration: Apache> - C<conf/httpd_modperl_solo.conf>
--- 153,158 ----
  determine the logging level for the whole server or discrete parts of
  it, which logfiles get written, when/if they're rolled over, etc. See
! L<OpenInteract2::Manual::Logging> for a quick intro to logging and
! read up about L<Log::Log4perl> for details.

  B<interface configuration: Apache> - C<conf/httpd_modperl_solo.conf>
***************
*** 169,173 ****
  (see C<conf/httpd_static.conf> for a proxy configuration and
  C<conf/httpd_modperl.conf> for the corresponding proxied backend
! configuration).

  B<interface configuration: standalone> - C<conf/oi2_daemon.ini>
--- 163,167 ----
  (see C<conf/httpd_static.conf> for a proxy configuration and
  C<conf/httpd_modperl.conf> for the corresponding proxied backend
! configuration). See L<OpenInteract2::Manual::AdminApache> for more.

  B<interface configuration: standalone> - C<conf/oi2_daemon.ini>