Greetings!
On 24 Apr, Dennis Gearon wrote:
> This is is how I believe that a site using Midgard application
> server is set up as far as abstraction layers, services supplies between
> components and hardware, and installation dependencies. To build this,
> start from the bottom. What I am not sure of is where PERL fits in if at
> all, if PHP is drawn into Midgard or Apache completely or it is still a
> seperate service of the Linux system, and if Midgard calls down to
> Apache or it is drawn into and part of Apache. Would someone on the list
> draw up a representative of how these relationships really are,
> including options? Thank you in advance.
Your diagram was mostly correct. However, here is how
the different Midgard components interact:
Midgard-Lib is the core Midgard library that handles
Midgard's interaction with the MySQL database, and
provides basic API for the other modules to use.
Midgard-PHP is a patched version of the regular PHP
module. It has functions for accessing parts of the
Midgard database through midgard-lib (like
mgd_get_article). Midgard-php works as a Apache module.
Mod_Midgard is a Apache module that handles catching
all URL requests for Midgard hosts and pages and
forwarding those to Midgard-PHP for processing. It also
uses Midgard-Lib for database connectivity.
> Dennis K. Gearon (Kegley)
/Bergie
--
-- Henri Bergius -- +358 40 525 1334 -- [EMAIL PROTECTED] --
http://www.iki.fi/Henri.Bergius
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]