Message-ID: <4868E580.8000904@hagander.net>
Date: Mon, 30 Jun 2008 15:54:08 +0200
From: Magnus Hagander <magnus@hagander.net>
User-Agent: Thunderbird 2.0.0.14 (X11/20080505)
MIME-Version: 1.0
To: Alvaro Herrera <alvherre@commandprompt.com>
CC: PostgreSQL WWW <pgsql-www@postgresql.org>
Subject: Re: [Pgweb] r2149 - in trunk/archives/html: . includes
References: <20080630131950.D5E5C1A3518@community1.commandprompt.com>
	<4868DECA.5060004@hagander.net>
	<20080630135212.GB10311@alvh.no-ip.org>
In-Reply-To: <20080630135212.GB10311@alvh.no-ip.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Alvaro Herrera wrote:
> 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.

Ah, so there's an ulterior motive :-)


> 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?

Shouldn't be, they're tiny.


> (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.)

Check. I absoluteliy don't mind getting it folded into using the
standard stuff.

//Magnus