From: JanWieck@t-online.de
To: PostgreSQL GENERAL <pgsql-general@postgresql.org>
To: PostgreSQL HACKERS <pgsql-hackers@postgresql.org>
To: PostgreSQL SQL <pgsql-sql@postgresql.org>
Subject: Re: lztext and compression ratios...
Date: Thu, 6 Jul 2000 10:47:24 +0200 (MEST)
Message-ID: <200007060847.KAA16369@hot.jw.home> (raw)
In-Reply-To: <10186.962836831@sss.pgh.pa.us>
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 #
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: JanWieck@t-online.de, pgsql-general@postgresql.org, pgsql-hackers@postgresql.org
Subject: Re: lztext and compression ratios...
In-Reply-To: <200007060847.KAA16369@hot.jw.home>
References: <10186.962836831@sss.pgh.pa.us> <200007060847.KAA16369@hot.jw.home>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox