From: | Dave Cramer <davecramer(at)gmail(dot)com> |
---|---|
To: | Steven Schlansker <stevenschlansker(at)gmail(dot)com> |
Cc: | Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: SCRAM inplementation |
Date: | 2017-04-02 21:04:13 |
Message-ID: | CADK3HHJHP26RB6QagodN0GfnVc9YANL9DdGt1Mdm+eNv27ZrpA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Dave Cramer
On 2 April 2017 at 14:51, Steven Schlansker <stevenschlansker(at)gmail(dot)com>
wrote:
>
> > On Apr 2, 2017, at 9:05 AM, Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>
> wrote:
> > On 31/03/17 14:31, Dave Cramer wrote:
> >>
> >> Also this means we are going to be adding some dependencies. Alvaro can
> you talk about which dependencies you are contemplating ?
> >
> >
> > So... I don't want to spur a heavy debate on Java6 vs Java8, and maybe
> that should go on a separate thread, but... thinking of it why not? There
> are indeed many versions (up to and including 42) of pgjdbc which work for
> Java6, are fully featured, and mature. While they are developed for a
> platform EOLed for several years. Does it make real sense to continue
> developing new versions with this platform in mind? Are there very strong
> reasons to remain Java6-compatible for future versions?
>
> One random $USER's opinion, Java 7 is already EOL. Why do we even talk
> about 6 anymore?
>
> If better or less code can be written, or reliability improved, by moving
> to Java 8 - do it! We should live in the future, not the past :)
>
>
Well we have to keep in mind that SCRAM is essentially an enterprise
feature, and like it or not there are lots of enterprises running on java 6
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2017-04-02 22:18:15 | Re: SCRAM inplementation |
Previous Message | Steven Schlansker | 2017-04-02 18:51:38 | Re: SCRAM inplementation |