pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Marko Kreen <markokr@gmail.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Euler Taveira <euler@timbira.com>
Cc: Florian Pflug <fgp@phlo.org>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>
Subject: Re: libpq compression
Date: Sat, 16 Jun 2012 00:40:15 -0400
Message-ID: <11141.1339821615@sss.pgh.pa.us> (raw)
In-Reply-To: <CACMqXCLg_HoaHZ1EiLdG+4zebQYK6OYFKPcdEg+jMkZ=u6ve7A@mail.gmail.com>
References: <4FD9698F.2090407@timbira.com>
	<29853.1339651170@sss.pgh.pa.us>
	<4FD9E70B.9040607@timbira.com>
	<11502.1339699384@sss.pgh.pa.us>
	<20120615021938.GA21704@momjian.us>
	<CABUevEyv4T+1gR6_Uqm_1qUD9PNDg6UdXbJhwHZgFi9hpQQ6NQ@mail.gmail.com>
	<F3B8BAA6-23E9-423A-A7D1-D2E14769F326@phlo.org>
	<CABUevExi-cJ6AvF2kDOy+qQsB+0JHofrcvVmNVoJ2HziZMMaAg@mail.gmail.com>
	<22690C61-E960-4A2A-BFD5-DAD3D3B5C474@phlo.org>
	<CABUevEzVpqS5RCLz2fFREdPFkuYkEKsrMpnfPixYWPki2=iJOA@mail.gmail.com>
	<4FDB954F.9010606@timbira.com>
	<CABUevEzvej-V0zfjdyK=BPmpD6DQO=6z2ohxd2HQTzoohQVt5Q@mail.gmail.com>
	<CACMqXCLg_HoaHZ1EiLdG+4zebQYK6OYFKPcdEg+jMkZ=u6ve7A@mail.gmail.com>

Marko Kreen <markokr@gmail.com> writes:
> On Sat, Jun 16, 2012 at 6:39 AM, Magnus Hagander <magnus@hagander.net> wrote:
>> Fair enough if we decide that - but we should make that decision
>> knowing that we're leaving the JDBC and .Net people in a bad position
>> where they are not likely to be able to implement his.
>> 
>> The JDBC people have a theoretical chance if the JDK is open. The .Net
>> people are stuck with schannel that doesn't support it at this point.
>> It might well do in the future (since it's in the standard); but
>> they're at the mercy of Microsoft.

> Both Java and C# are open-source enough that anybody can
> take existing SSL implementation and add compression to it,
> then distribute it as improved SSL library.

Possibly more to the point: that is work they might have to do, if
nobody else steps up to the plate --- and if they do end up doing it,
it could benefit other projects too.  On the other hand, if we
roll-our-own transport compression solution, that is work they *will*
have to do, with no chance of sharing the effort with other projects.

BTW, as far as the .Net case goes, it took only a moment's googling
to find this:
http://openssl-net.sourceforge.net/
which is a .Net wrapper around real OpenSSL.  It doesn't appear to
provide wrappers for the compression selection functions, but surely
that's just a lack of round tuits, not that it would take more than
five minutes to add them.

			regards, tom lane



view thread (289+ messages)  latest in thread

Message-ID: <11141.1339821615@sss.pgh.pa.us>
Permalink:  ../11141.1339821615@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/11141.1339821615@sss.pgh.pa.us

 · 

reply
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 using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, markokr@gmail.com, magnus@hagander.net, euler@timbira.com, fgp@phlo.org, bruce@momjian.us
  Subject: Re: libpq compression
  In-Reply-To: <11141.1339821615@sss.pgh.pa.us>

* 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