Skip to content

Auth handler per connection #1473

Answered by florimondmanca
jborean93 asked this question in Q&A
Discussion options

You must be logged in to vote

Hey @davidbgk

This is a very interesting scenario.

I believe the transport route is the most promising. The "wrap / unwrap" thingy you do there for example screams for "wrap the request / response stream" at the transport level. :)

But I wouldn't do subclassing. Instead I think you might be able to get something working by composing with an existing transport, and then wrapping things however is necessary to accommodate your auth scheme. You might not even need to modify the pool, and instead do the tracking of origins inside your own transport.

I can draft some code snippets to help you out with this intuition later if you'd like. :)

Replies: 1 comment 9 replies

Comment options

You must be logged in to vote
9 replies
@jborean93
Comment options

@jborean93
Comment options

@jborean93
Comment options

@florimondmanca
Comment options

@jborean93
Comment options

Answer selected by jborean93
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants