jrhee17

Thrift as many know is a RPC framework. Armeria supports thrift on top of its HTTP stack, and basic usage can be found by following the [tutorial](https://armeria.dev/tutorials/thrift/blog). Thrift is known...

Hey, sorry about the late update. So talked with the team and a couple of ideas: I think one of the concerns was autocompletion for the wrong schema which may...

Haven't forgotten about this issue, but there's a lot going on at the moment 😅 Let me try to brainstorm a little more before the next release

> Would be awesome if we could opt-in for original percent encoding on per route basis on a server While looking at this comment, it seems at the moment there...

Talked with the others, I propose the following: ##### Server side A new method is added such that the original (raw) path of the request can be retrieved to `ServiceRequestContext`....

> Is the information on where the exception was thrown included in stack trace? Do you intend to add other information? This was just an idea I had which turned...

Sorry about the delay, how about: - We don't try to migrate all exceptions, but just focus on request binding exceptions in annotated service and expand from there? - We...

Thanks! I think we probably want to solve this using a decorator like we did for `RetryingClient`. Implementation-wise I think we need to decide whether to add a new `HedgingClient`...

> So, for the case of makeContextAware(ExecutorService), instead of separately passing an exception handler as a parameter, I considered adding submit(Callable, Function) to ContextAwareExecutorService interface. I would like to know...

Talked with @ikhoon What do you think of: - Instead of adding a method to `WebClient`, create a decorator `HeadersUpdatingClient` which updates headers of requests - If a `CompletableFuture` fails,...