Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TrxiY-0007io-IJ for pgsql-www@arkaria.postgresql.org; Sun, 06 Jan 2013 21:25:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TrxiX-0005qS-K3 for pgsql-www@arkaria.postgresql.org; Sun, 06 Jan 2013 21:25:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TrxiW-0005qM-Tk for pgsql-www@postgresql.org; Sun, 06 Jan 2013 21:25:17 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TrxiT-0000DM-Qk for pgsql-www@postgresql.org; Sun, 06 Jan 2013 21:25:16 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id r06LP8xp006905; Sun, 6 Jan 2013 16:25:08 -0500 (EST) From: Tom Lane To: Magnus Hagander cc: Greg Stark , Peter Geoghegan , PostgreSQL WWW Subject: Re: New archives for testing In-reply-to: References: <18383.1357499527@sss.pgh.pa.us> Comments: In-reply-to Magnus Hagander message dated "Sun, 06 Jan 2013 22:12:44 +0100" Date: Sun, 06 Jan 2013 16:25:08 -0500 Message-ID: <6904.1357507508@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-www Precedence: bulk Sender: pgsql-www-owner@postgresql.org Magnus Hagander writes: > On Sun, Jan 6, 2013 at 9:59 PM, Greg Stark 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 -- Sent via pgsql-www mailing list (pgsql-www@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www