On 03/04/17 00:18, Simon Riggs wrote:
> On 2 April 2017 at 17:05, Álvaro Hernández Tortosa <aht@8kdata.com> wrote:
>
>> * Write both a client and server implementation. pgjdbc will only require
>> the former, of course, but having both will be great for testing.
>> * Do so as an independent library, also as an independent repository on
>> Github. This will help its reuse and testing by independent projects. I
>> presume it will have at least three different artifacts, a scram-common,
>> scram-server and scram-client. Only the latter will be directly imported as
>> a direct dependency by pgjdbc.
> Don't see any need for the external stuff. We just want a patch on the
> driver so any external dependencies are minimized, so we retain full
> control over what the driver is doing.
Hi Simon.
It's not that is a need. Its that it is what should be. Code
re-utilization and sharing across different projects is mutually
beneficial. C might not make this easy (it doesn't) but Java does and it
should be leveraged. A specific external SCRAM project encourages other
to use it, improve it, test it, outside our limited capabilities.
I don't buy how this would mean less control over what the driver
is doing. Code is open source, BSD license, either patches or forks
could be created.... and it will be designed initially for pgjdbc needs.
That's all we need, I believe.
> That can be reused easily
> enough in other projects, if they wish.
How? Copy and paste the code somewhere else? This is exactly what I
want to avoid. What if others find this functionality interesting? I
think this method of being an external project favors sharing and
collaboration among open source communities.
>
> Thanks for offering to write a patch.
>
Thanks for all the patches you have written so far ^_^
Álvaro
--
Álvaro Hernández Tortosa
-----------
<8K>data