More CGI Stuff

[Pierre Sahores]

Phil Davis a écrit :
> 
> ----- Original Message -----
> From: "David Bovill" <david.bovill at opn-technologies.com>
> To: <metacard at lists.runrev.com>
> Sent: Friday, August 30, 2002 11:33 AM
> Subject: Re: More CGI Stuff
> 
> > On Fri, 2002-08-30 at 16:13, Yennie at aol.com wrote:
> > > >
> > > Unfortunately, no- the server will spawn a new cgi process for each request.
> > > I have found a couple options, however:
> > >
> > > 1). Run a simple server which takes request from cgi scripts (over sockets),
> > > and supplies the persistent data.
> > >
> > > 2) Run a pool of servers, all listening on their own port, and then still
> > > utilize 1).
> > >
> >
> > With 2) is the idea to have the cgi script switch on each call to
> > another process?
> >
> > > I did cook up something fun to play with. I stuck this in a script "httpd"
> > > and call "./httpd 8080 10" from the terminal. What I get: 10 processes
> > > listening on ports 8080-8089.
> > >
> >
> > Re: my recent post are you using 2.4.3 with httpd? Having problems with
> > my server under 2.4.3...
> >
> > In terms of IAC - which is what you are doing here right? Do you have
> > any info regarding performance and the various techniques that are
> > possible (in particular using an external, shell, and sockets)- what do
> > you think:
> >
> > 1) Shell (slowest)
> >
> > 2) Sockets
> >
> > 3) Externals (any faster?)
> >
> 
> FWIW, I believe Pierre Sahores explained a way to use PHP to manage sockets and enable backend use of MC as a long-running process. I think it's related to this thread. (Wherever that explanation is in the archives, maybe Ken Ray would consider adding it to his already excellent Developer Resources section at http://www.sonsothunder.com !)
> 
> Phil
 
Hi Friends, Hi David,

That's trough : under unixes, including Linux, xBSD, Solaris and
probably MacOSX (just tested for yet in graphical mode), Metacard is
able to run, in both console or graphical modes, as a backend deamon,
just alike Apache or PostgreSQL. As Metacard is able to reply (with 100%
of succes) to tcp/ip sockets messages, we have just to use a small
cgi-script (.php than .mt prefered there) to bind Apache to the Metacard
application server.

As we can include in the small .php cgi script different "case of/socket
port" statements, we can have more than a Metacard application server
waiting for messages behind Apache, each one using a different port
(under 1025 in root/console mode, over 1024 in user/graphical mode).

The key points of the use of MC in this way is that it make us able to :

1.- build generic web and vpn applications servers able to store, betwin
and along incoming queries, globals vars datas status in RAM ;
2.- think the application logical architecture before binding it to
custom-props, files-based or SQL-based databases ;
3.- get more power and security in writting clean and reusable code than
in using J2EE-based applications servers ;
4.- bind (directly, trough PHP or shell commands) to SQL servers each
time we need to avoid to store to much datas in RAM (PostGreSQL greatly
prefered there) ;
5.- run multi-threaded networked apps (up to 800 connections/secs on a
Linux Suse 6.3 ATHLON 800 with 1Go of RAM/SWAP) in letting Apache/PHP
open and manage multiple connections to the MC-based web application
server ;
6.- ddevelopp once, install anywehre, even on the win2000 and up
platform.

Even in this kind of stuffs, Metacard can do us able to build the best
professionnal apps. MC just let us think them :)

I can, if needed, rewrite a resume of the detailled ways i use to set-up
those kind of MC apps.

-- 
Cheers, Pierre Sahores

Inspection académique de la Seine-Saint-Denis

Synthétiser et produire l'avantage compétitif
Serveurs d'applications & de bases de données