Date: 2020-04-08 08:30:54
> -----Original Message-----
> From: Boost <boost-bounces_at_[hidden]> On Behalf Of Ruben Perez via Boost
> Sent: 7 April 2020 19:58
> To: boost_at_[hidden]
> Cc: Ruben Perez <rubenperez038_at_[hidden]>
> Subject: Re: [boost] MySQL ASIO library
> What I don't want is to assume the responsibility for implementing all the
> backends in the world, because then the project is going to die before achieving
> anything useful. It has been an awful amount of work implementing (and testing)
> the MySQL backend - I don't think a single person alone is able to implement all
> the backends. From this point of view, I agree with Richard in making each
> backend a separate library. Unless somebody offers their help ;)
There would certainly not be any expectation that you would single-handedly write and/or maintain more than on backend!
I can sense that a lot of work has gone into this already ð
If you are willing to take on the BIG challenge - something that would be MUCH more valuable long-term,
you might like to consider seeking a 'partner' who would work to develop a second backend on their favorite SQL.
(You might change the title to Boost.SQL too? Or Boost.SQL-ASIO? Since its USP seems to be ASIO.)
> BTW, I have implemented TLS connections and widened the authentication
> method support. I have also made available some online documentation - may
> provide a better understanding a library for you all. You can check it
> here: https://anarthal.github.io/boost-mysql-docs/index.html
Really nice docs and convincing examples (to a non-expert).
I feel I could dive into this and get going (but then fools step in where angels fear to tread!)
PS You really should make clear that this is not *yet* a Boost library, but I really hope it will become one.
The attached logo might help, or a line of text saying 'Proposed for Boost'.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk