Re: New archives for testing

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

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

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.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Tom Lane 2013-01-06 21:25:08 Re: New archives for testing
Previous Message Greg Stark 2013-01-06 20:59:13 Re: New archives for testing