Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by hub.org (8.10.1/8.10.1) with ESMTP id e66ALfS85105; Thu, 6 Jul 2000 06:21:42 -0400 (EDT) Received: from fwd05.sul.t-online.com by mailout02.sul.t-online.com with smtp id 13A8mr-0004TD-03; Thu, 6 Jul 2000 12:21:41 +0200 Received: from hot.jw.home (340000654369-0001@[62.224.112.78]) by fwd05.sul.t-online.com with esmtp id 13A8mZ-1S1rlpC; Thu, 6 Jul 2000 12:21:23 +0200 Received: (from wieck@localhost) by hot.jw.home (8.8.5/8.8.5) id KAA16369; Thu, 6 Jul 2000 10:47:24 +0200 From: JanWieck@t-online.de (Jan Wieck) Message-Id: <200007060847.KAA16369@hot.jw.home> Subject: Re: lztext and compression ratios... In-Reply-To: <10186.962836831@sss.pgh.pa.us> from Tom Lane at "Jul 5, 2000 06:40:31 pm" To: PostgreSQL GENERAL , PostgreSQL HACKERS , PostgreSQL SQL Date: Thu, 6 Jul 2000 10:47:24 +0200 (MEST) Reply-To: Jan Wieck X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Sender: 340000654369-0001@t-dialin.net X-Archive-Number: 200007/222 Tom Lane wrote: > JanWieck@t-online.de (Jan Wieck) writes: > > One thing to keep in mind is that the LZ algorithm you're > > thinking of must be distributable under the terms of the BSD > > license. If it's copyrighted or patented by any third party, > > not agreeing to these terms, it's out of discussion and will > > never appear in the Postgres source tree. Especially the LZ > > algorithm used in GIF is one of these show-stoppers. > > As long as you brought it up: how sure are you that the method you've > used is not subject to any patents? The mere fact that you learned > it from someone who didn't patent it does not guarantee anything --- > someone else could have invented it independently and filed for a > patent. Now that you ask for it: I'm not sure. Could be. > If you can show that this method uses no ideas not found in zlib, > then I'll feel reassured --- a good deal of legal research went into > zlib to make sure it didn't fall foul of any patents, and zlib has > now been around long enough that it'd be tough for anyone to get a > new patent on one of its techniques. But if SLZ has any additional > ideas in it, then we could be in trouble. There are an awful lot of > compression patents. To do so I don't know enough about the algorithms used in zlib. Is there someone out here who could verify that if I detailed enough describe what our compression code does? Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #