public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: Tom Lane <[email protected]>
Cc: Greg Stark <[email protected]>
Cc: Peter Geoghegan <[email protected]>
Cc: PostgreSQL WWW <[email protected]>
Subject: Re: New archives for testing
Date: Sun, 6 Jan 2013 22:46:13 +0100
Message-ID: <CABUevEyeVefgbgADB+moU_b889a57bsWip+=2r0h1uuV5KwLqw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CABUevEwmR5+9fc1i1cFVpc1S8XShHwvKopcaKKfq-Txa+_mq_g@mail.gmail.com>
<[email protected]>
<CABUevEzx8tAUZErb8PhADj=mzSEUdUE8-ueqUfuP=mnNjbMQ3A@mail.gmail.com>
<CAEYLb_UWpcNdyEHzOyzGYs9+CEXqrNP8-c5tPd6X9v1fK9jKYQ@mail.gmail.com>
<CABUevExrSBxtW3qkUA7-cn=DFTVVdcahDpWFovMcWOnRxf=ZhQ@mail.gmail.com>
<CAM-w4HOUE2v_d1xhZOTk930ugu2UiAQbHLy41DjUiZtT355KAg@mail.gmail.com>
<CABUevEznc2gdDdOEqDkNM4sjXWwQMvDWvE6j0_8TAyf3+=ZEZQ@mail.gmail.com>
<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-www>
On Sun, Jan 6, 2013 at 10:25 PM, Tom Lane <[email protected]> wrote:
> Magnus Hagander <[email protected]> writes:
>> On Sun, Jan 6, 2013 at 9:59 PM, Greg Stark <[email protected]> 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 ...
Yeah, I was thinking scrollbars rather than cut. Turns out the
max-width option actually rescales the image, so we're fine.
I've applied a change that makes it now inline all images <75kb, and
rescaling them down to 600 pixels wide if they are bigger.
The example URL you used have been reloaded from the new code, so it
shows what it looks like. Any other pages that had images on them that
were already viewed are currently cached the old way, but will
automatically update once they expire from the cache (max 4 hours).
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-www mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www
view thread (37+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: New archives for testing
In-Reply-To: <CABUevEyeVefgbgADB+moU_b889a57bsWip+=2r0h1uuV5KwLqw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox