Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 18442 invoked by uid 500); 18 Sep 2000 18:22:54 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 18317 invoked from network); 18 Sep 2000 18:22:48 -0000 From: TOKILEY@aol.com Message-ID: <48.b03bf6d.26f7b759@aol.com> Date: Mon, 18 Sep 2000 14:22:17 EDT Subject: Re: [Fwd: png icons for apache] To: new-httpd@apache.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 3.0 16-bit for Windows sub 86 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N In a message dated 00-09-18 13:49:12 EDT, J. Sutherland writes. > Why bother? If we want PNGs, just convert the GIFs to PNGs once. > Much more efficient. Absolutely... but I was proposing something that would solve the problem for everyone if/when the .GIF bomb explodes, not just Apache. It's worse than you think. MANY sites are actually building the .GIF images dynamically ( advertisers, for example ) when requested and they never acually exist as files. For them it's a major codebase re-write... unless they have some filtering available to do the real-time conversions for them 'on the fly'. Yours... Kevin Kiley CTO, Remote Communications, Inc. http://www.RemoteCommunications.com/ http://www.RemoteCommunications.com/rctpd/ - Free IETF encoding Server