Re: Question: merit / feasibility of compressing frontend

Joshua D. Drake <jd@commandprompt.com>

From: "Joshua D. Drake" <jd@commandprompt.com>
To: Justin Clift <justin@postgresql.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Doug McNaught <doug@wireboard.com>, Bruno Wolff III <bruno@wolff.to>, Chris Albertson <chrisalbertson90278@yahoo.com>, Neil Conway <nconway@klamath.dyndns.org>, <pgsql-general@postgresql.org>
Date: 2002-07-17T08:32:10Z
Lists: pgsql-general
> If someone's willing to put the time into this, then compression without
> SSL feels like a good idea.  Not everyone uses SSL.  Bad network latency

Well, we are already putting the time into it ;). I expect to have it 
complete by the end of the week. If people like we can keep in touch about 
it. 

Sincerely,

Joshua Drake



> has a very undesirable effect on the establishment of SSL connections,
> and this is especially of interest in those cases where people need to
> get short "bursty" amounts of SQL data across a connection as fast as
> possible.  Aka, client using a frontend app to remote databases over a
> modem, and not using persistent connections.
> 
> Establishment of an individual SSL session using OpenSSL can take over a
> second in this case.  Not consistently-always, but I had to time it (on
> fast hardware too) for a contract recently when deciding on network
> layer transports.
> 
> Hope this gives some decent food for thought.
> 
> :-)
> 
> Regards and best wishes,
> 
> Justin Clift
>  
> >                         regards, tom lane
> > 
> > ---------------------------(end of broadcast)---------------------------
> > TIP 2: you can get off all lists at once with the unregister command
> >     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
> 
>