Re: New archives for testing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Greg Stark <stark(at)mit(dot)edu>, Peter Geoghegan <peter(at)2ndquadrant(dot)com>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>
Subject: Re: New archives for testing
Date: 2013-01-06 21:25:08
Message-ID: 6904.1357507508@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Sun, Jan 6, 2013 at 9:59 PM, Greg Stark <stark(at)mit(dot)edu> wrote:
>> 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?

> That's certainly another option - limit it by size that way, and then
> limiting it by filesize for whether we include it or not. We can even
> give it scrollbars, I guess. That does make even more sense.

A file-size-based limit on what we'll inline seems perfectly sensible
from here. As for scrollbars, if it's big enough to need those, we
probably don't want it inline ...

regards, tom lane

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2013-01-06 21:46:13 Re: New archives for testing
Previous Message Magnus Hagander 2013-01-06 21:12:44 Re: New archives for testing