Creating many “clients” vs wrapping a “client” in an actor

[taylorswift]

@lukasa

This is accurate: ClientBootstraps are cheap, feel free to create plenty.

i see, i was creating NIOSSLContext in the same function, as i was conceptualizing SSL context creation and bootstrap creation as “expensive, do-once” tasks to be grouped together. but if ClientBootstraps are cheap to make, i might as well separate the SSL context creation from the bootstrap creation.

the documentation really emphasizes the importance of creating ClientBootstrap once and reusing it, i think this advice is unhelpful and caused me to spend a lot of time optimizing something that didn’t need to be optimized.

@sliemeobn

I'm not quite sure I understand what you mean by "separate, dedicated clients" in this context, because im my mind this has nothing to do with bootstraps but rather channels.

in this context, a “client” is just a type that wraps some value parameters (API key, account ID, etc.) and a ClientBootstrap. a “client” can be reused multiple times to connect to the same server.