In async Java it seems like libraries take one of three paths when it comes to custom executor support:
1) don't support specifying the executor, which puts everything into the ForkJoinPool commonPool
2) use a builder for the client itself, and allow setting an executor there (ex AWS Java SDK)
3) every async method has a blahAsync version that takes an executor to run on
Right now we're doing 1. Either of the others seem like significant work, but the feature is needed for users to control whether their CFs run on blocking threadpools etc.
Determine what method users would prefer and the feasibility of implementing it. Make a scoped ticket for implementation.
See https://github.com/IronCoreLabs/uniffi-bindgen-java/pull/10#discussion_r1631617076 for some context.
In async Java it seems like libraries take one of three paths when it comes to custom executor support:
1) don't support specifying the executor, which puts everything into the
ForkJoinPool commonPool
2) use a builder for the client itself, and allow setting an executor there (ex AWS Java SDK) 3) every async method has ablahAsync
version that takes an executor to run onRight now we're doing 1. Either of the others seem like significant work, but the feature is needed for users to control whether their CFs run on blocking threadpools etc.
Determine what method users would prefer and the feasibility of implementing it. Make a scoped ticket for implementation.