Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TrxWV-0007Wg-9C for pgsql-www@arkaria.postgresql.org; Sun, 06 Jan 2013 21:12:51 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TrxWU-0004UG-9Z for pgsql-www@arkaria.postgresql.org; Sun, 06 Jan 2013 21:12:50 +0000 Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TrxWS-0004Tz-HF for pgsql-www@postgresql.org; Sun, 06 Jan 2013 21:12:48 +0000 Received: from mail-wg0-f54.google.com ([74.125.82.54]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TrxWQ-0004a8-IJ for pgsql-www@postgresql.org; Sun, 06 Jan 2013 21:12:47 +0000 Received: by mail-wg0-f54.google.com with SMTP id fg15so8862237wgb.33 for ; Sun, 06 Jan 2013 13:12:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=z09gEyYvYJFZHxawCbgPXt+3DmgJdX6Qi1NwQfbq9F4=; b=CzQ6p4ppn3jGG4wtJqT7I0aijDTmz56ZnMsGxMRBV53xbGJ0mMIXIPPtFhRnKEnC/B E9dovRDz8KbyVVtVBqiJn4f1m309mVRSFgxpIegsFbFEspOVQ3rHPd0CW1AaXWPaMlTX Bko+L9Fd14269dwNk1IhwWNvjroRUP3RAKCQL8Qc9mqEvqAZarhd/hUp6SW00a+bG2+M tWJ9oRo+aTFwKwKnX5GdWzly40UNir0Q7LG6MFbK5A37caFb/Zt1UMqQ13h0UDvbT2GX V4OhPm2dRq+GKJnxRRowxa15QWeAwEbKr19cBtpo81SvYy0gqbW8pEynVSmt5K8n8Mzr oqog== MIME-Version: 1.0 X-Received: by 10.180.102.170 with SMTP id fp10mr1951999wib.13.1357506764843; Sun, 06 Jan 2013 13:12:44 -0800 (PST) Received: by 10.194.104.41 with HTTP; Sun, 6 Jan 2013 13:12:44 -0800 (PST) In-Reply-To: References: <18383.1357499527@sss.pgh.pa.us> Date: Sun, 6 Jan 2013 22:12:44 +0100 Message-ID: Subject: Re: New archives for testing From: Magnus Hagander To: Greg Stark Cc: Peter Geoghegan , Tom Lane , PostgreSQL WWW Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlYBNRlgxkl0frCJkBayK1SgStknWGRbWpb3AMt0kI/BkiVCxj4k8v5ZgJ48mWjjx36K3oz X-Pg-Spam-Score: -2.6 (--) 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 On Sun, Jan 6, 2013 at 9:59 PM, Greg Stark wrote: > On Sun, Jan 6, 2013 at 8:53 PM, Magnus Hagander 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/ -- Sent via pgsql-www mailing list (pgsql-www@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www