Thanks for taking the time to make this proposal. At this time, I don't really have an strong opinions on how connection pools should work - I will think on it some more this week. I'd agree that the driver is hard to configure and perhaps all that flexibility that currently exists results in too much low-level knob turning that is hard for the average user to reason about. So a more simple set of configuration options and hopefully a more simple to maintain code base without (1) a noticeable loss in performance or (2) breaking change in protocol would probably be well received by the community. I think it would be important for a PR of this scope to have some performance comparisons presented when the changes are in place and ready for a PR to review.
I sense that as this is a large change that it should slate for 3.5.0 (which we really haven't even begun to plan yet, but perhaps this is the catalyst to start talking about that). On Fri, Mar 15, 2019 at 9:36 PM Divij Vaidya <[email protected]> wrote: > Hello all, > > I would like to propose an implementation change on the Gremlin Java > client. The change impacts the connection pool management and configuration > of the client. The following document discusses the problems that the > change is trying to address along with the proposed solution. > > > https://docs.google.com/document/d/1MG6dx-h-lfmc6d469ZXfDBeGM_ivBcWi7sziC-jLJNw/edit?usp=sharing > > Kindly review the document and let me know about your suggestions/concerns. > > Once the proposal is approved, I will work on the implementation of the > proposal and file a pull request with the relevant code changes. > > Regards, > Divij Vaidya >
