In my scenario I need to do some work on the new TCP connection before using the socket of the chained proxy(state authentication).. In order to do that I had to expose few classes as public, and to add a new method to the ChainedProxy interface: ConnectionFlowStep customConnectionFlow(ProxyConnection connection);

Will you be interested in a PR?

Hello Almog,

thank you very much! Yes, PRs are always welcome. It's interesting to
see new ideas and requirements.

But I think, this could lead to a breaking change. I know, Jason @jekh
is wondering about refactoring the connection flow. I'm evaluating some
ideas here:

 https://github.com/ganskef/shortcircuit-proxy

Regards Frank

Am 04.07.2016 um 17:51 schrieb Almog Baku:

In my scenario I need to do some work on the new TCP connection before
using the socket of the chained proxy(state authentication).. In order
to do that I had to expose few classes as public, and to add a new
method to the |ChainedProxy| interface: |ConnectionFlowStep
customConnectionFlow(ProxyConnection connection);|

Will you be interested with PR?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#306 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AKIGhgQfGvBdGFN7VzhQmznQvhMFm-QPks5qSSwagaJpZM4JEbyV.

I'd love to see some ideas around the ConnectionFlow refactoring. I've been pondering this for months, but I don't have any fully-baked ideas yet. I won't be able to start devoting significant time to it until this fall, so anybody who has some thoughts, please do share!