From 17fa9b2b04bfdc14cf61d2aaf89d4a4af964e9c6 Mon Sep 17 00:00:00 2001 From: "ken.lj" Date: Sat, 29 Dec 2018 17:06:48 +0800 Subject: [PATCH] Update README.md --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 3d3f246..b212cff 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ There will have two parts in this repo * AsyncSignal class specially designed to distinguish async method. * A compiler hacker processer that is able to generate async counterpart for each method in you Dubbo service interface. - + ## AsyncSignal AsyncSignal is an optional convenient type provided to unify your service definitions. @@ -30,3 +30,6 @@ Now, you can call the new method with the CompletableFuture signature directly o ## Compiler hacker processer It should run at compile time, and overwrite each method in your service definition with an async equivalence. I think we can try to realize it by referencing [lombok](https://projectlombok.org/). + +# Conclude + The essential part is to overwrite a new async method. Another way would be to generate a new method with a different name, for example, `sayHiAsync`, then we can get rid of `AsyncSignal`. But there's an obvious flaw of this way, that is, all method level configurators and routers defined to `sayHi` will not take effect.