Date: Mon, 30 Jun 2008 09:52:12 -0400
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: PostgreSQL WWW <pgsql-www@postgresql.org>
Subject: Re: [Pgweb] r2149 - in trunk/archives/html: . includes
Message-ID: <20080630135212.GB10311@alvh.no-ip.org>
References: <20080630131950.D5E5C1A3518@community1.commandprompt.com>
	<4868DECA.5060004@hagander.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4868DECA.5060004@hagander.net>
User-Agent: Mutt/1.5.18 (2008-05-17)

Magnus Hagander wrote:
> What's the reason for this? :-)
> 
> Keeping it on the main website gets you the global distribution for
> faster access, and also better caching for people... Is there any reason
> not to use that?

Also, in order to fix the hardcodedness of lists in the archives pages, 
I need a templating system; and what better idea than to just reuse the
PgPage stuff?  So I was considering using svn:externals to get
portal/system/global and pearlib/ into trunk/archives, so that a
checkout of archives gets the needed files.

The downside is that if somebody checks out pgweb:trunk/ then he will
get those files twice.  Is that too much of a problem for anyone?


(Before anybody complains about the extra load, I'm not planning to use
the templating stuff for every page load -- only to generate some
includes when the list of lists changes.  This probably means that it
will be cheaper than the current code, because most of it will be plain
HTML instead of having some embedded PHP.)

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.