MIME-Version: 1.0
In-Reply-To: 
 <CABUevEzx8tAUZErb8PhADj=mzSEUdUE8-ueqUfuP=mnNjbMQ3A@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>
Date: Sun, 6 Jan 2013 20:51:54 +0000
Message-ID: 
 <CAEYLb_UWpcNdyEHzOyzGYs9+CEXqrNP8-c5tPd6X9v1fK9jKYQ@mail.gmail.com>
Subject: Re: New archives for testing
From: Peter Geoghegan <peter@2ndquadrant.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: 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 6 January 2013 20:41, Magnus Hagander <magnus@hagander.net> wrote:
> We could inline all images, with that risk. Or maybe we could actually
> parse the image to figure out it's size, and show it only when it's
> smaller than a certain size. That might be a useful compromise...

How likely is it in practice that an image is any other type of image?
Ideally, you'd be able to do something with the image metadata to
inline an image if its resolution is below a certain threshold. If
that doesn't work out, I'd just inline png, gif and svg images, and
leave it at that.

-- 
Peter Geoghegan       http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services


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