MIME-Version: 1.0
In-Reply-To: 
 <CABUevExrSBxtW3qkUA7-cn=DFTVVdcahDpWFovMcWOnRxf=ZhQ@mail.gmail.com>
References: 
 <CABUevEwmR5+9fc1i1cFVpc1S8XShHwvKopcaKKfq-Txa+_mq_g@mail.gmail.com>
	<18383.1357499527@sss.pgh.pa.us>
	<CABUevEzx8tAUZErb8PhADj=mzSEUdUE8-ueqUfuP=mnNjbMQ3A@mail.gmail.com>
	<CAEYLb_UWpcNdyEHzOyzGYs9+CEXqrNP8-c5tPd6X9v1fK9jKYQ@mail.gmail.com>
	<CABUevExrSBxtW3qkUA7-cn=DFTVVdcahDpWFovMcWOnRxf=ZhQ@mail.gmail.com>
From: Greg Stark <stark@mit.edu>
Date: Sun, 6 Jan 2013 20:59:13 +0000
Message-ID: 
 <CAM-w4HOUE2v_d1xhZOTk930ugu2UiAQbHLy41DjUiZtT355KAg@mail.gmail.com>
Subject: Re: New archives for testing
To: Magnus Hagander <magnus@hagander.net>
Cc: Peter Geoghegan <peter@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>,
	PostgreSQL WWW <pgsql-www@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Precedence: bulk
Sender: pgsql-www-owner@postgresql.org

On Sun, Jan 6, 2013 at 8:53 PM, Magnus Hagander <magnus@hagander.net> wrote:
> Well, that's what I'm considering, but inlining screenshots at high
> resolutions is going to look Really Bad... But yes, the idea would be
> to parse out the resolution from the metadata somehow.

I would be more concerned with the file size. You don't want someone
to be able to make an archive page send a hapless viewer a 100M image
file. Luckily file size doesn't require parsing the meta data.

Can you not deal with the image size by just sticking a css attribute
for max-height and max-width on the inlined image?

-- 
greg


-- 
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www