Heads up—

I have an KahaDB extensibility PR pushed up that simple changes visibility to 
allow for a subclass of KahaDB to live in a separate package. This opens the 
door to consider a new implementation making non-subtle changes without having 
to try to clutter the existing implementation or risk existing KahaDB 
stability.  

Specifically — Virtual Threads and aio capabilities for consideration in the 
form of a follow-on.

Thanks!
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to