Re: pgfoundry moved ...

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su>, "Magnus Hagander" <mha(at)sollentuna(dot)net>
Cc: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, "Gavin M(dot) Roy" <gmr(at)ehpg(dot)net>, "Josh Berkus" <josh(at)agliodbs(dot)com>, <pgsql-www(at)postgresql(dot)org>
Subject: Re: pgfoundry moved ...
Date: 2005-04-30 10:34:08
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4850750@ratbert.vale-housing.co.uk
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-www

-----Original Message-----
From: Oleg Bartunov [mailto:oleg(at)sai(dot)msu(dot)su]
Sent: Fri 4/29/2005 8:11 PM
To: Magnus Hagander
Cc: Dave Page; Marc G. Fournier; Gavin M. Roy; Josh Berkus; pgsql-www(at)postgresql(dot)org
Subject: Re: [pgsql-www] pgfoundry moved ...

> Ok, I think it's bad architecture. I already told Marc about that.
> It's very easy to separate processing binary static files like images from
> dynamic content. Just setup thttpd. Next step to setup frontend web server
> which should be very light with cacheing capability - we use mod_accel module
> for apache. It's frontentd which communicate with browser (probably slow link).
> Backend, with PHP, mod_auth_pgsql should be use for page generation, it
> should communicate only with frontend. The main idea is that you need much
> less backends (plus postgres connection for each backend), so much lesser
> resources will be used. What's the problem to setup this ?

This is irrelevant to svr2.

Regards, Dave

Browse pgsql-www by date

  From Date Subject
Next Message Dave Page 2005-04-30 10:37:13 Re: New window for search results
Previous Message Marc G. Fournier 2005-04-30 00:22:42 borg.postgresql.org upgrade