TTL v3 项目管理

TTL core

API incompatible upgrade

❗️ Incompatible

• ✨ Rename TransmittableThreadLocal#copy method to transmiteeValue
  • Although in most cases, the value being passed is a complex object, it is common to think of copying it, such as deep copying or shallow copying. The method copy is easy to think of and understand the process and operation involved.
  • This is also why the method was named copy in TTL v2.
  • The name transmiteeValue is consistent with the method name InheritableThreadLocal.childValue() in the JDK.
• ✨ Remove TransmittableThreadLocal's before/after execute methods
  • The TransmittableThreadLocal class is the user API of TTL, and it should be as simple as possible, containing only the core functionality (not peripheral or optional functionality).
  • The before/after execute callbacks are supported by the Transmitter through registration.
  • More discussion
  • https://GitHub.com/alibaba/transmittable-thread-local/issues/377#issuecomment-1107827776
  • https://GitHub.com/alibaba/transmittable-thread-local/issues/377#issuecomment-1107832086
• Move the inner class TTL Transmitter under the root package, making it a subpackage called transmitter
  • Instead of an inner class, the core concept is not a first-class citizen.
  • This also leads to the TransmittableThreadLocal class file becoming longer and longer…
• ✨ #168
  • The CRR method of TTL Transmitter returns a specific type, not Object.
• Delete (hidden) interfaces (these were not open interfaces in the first place, and deleting the implementation makes it simpler)
  • Delete (hidden) DisableInheritableThreadFactory interface
  • Delete (hidden) DisableInheritableForkJoinWorkerThreadFactory interface
• Reduce the number of utility methods to simplify the API
  • In v2, the number of utility methods was excessive due to the switch parameters.
  • reduce util