We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No description provided.
The text was updated successfully, but these errors were encountered:
Below discussions are Chinese, need be rewritten by English later 💕
Java
Java有繁荣的代理库,如
这些代理(AOP)因为没有 wrapper(链)规范,不透明。 这里的不透明是指,代理所加强的功能是什么、underlying instance是什么。
因为wrapper(链)不透明,
这些AOP代理的业务能力增加,作为实现者 是可以反向识别(即功能是什么、underlying instance是什么)
wrapper规范 应该通过SPI 加载 不同的识别功能,完善已有wrappers实现的wrapper链。
wrain现在的实现(v0.3.0)只是识别能力(即SPI要扩展的功能)的缺省实现, 即能识别 直接继承了Wrapper规范接口了实现
v0.3.0
对了,这个库的命名,可以模仿reactive streams,命名成inspectable-wrappers。
reactive streams
inspectable-wrappers
为什么不命名成 chainable wrappers? 因为用不用这个库,实际 wrappers 都是 chained的。
chainable wrappers
Sorry, something went wrong.
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: