灵珑·蜕变

[knight6236]

Welcome to LingFrame V0.2.0! This major update signifies the project's pivotal evolution from "fundamental runtime isolation" toward full-spectrum Runtime Resilience Governance (Phase 3). Additionally, we've executed a massive terminology refactoring, rigorously addressed classloader memory leak scenarios, and dramatically expanded ecosystem compatibility to legacy environments.

🎉 Key Highlights

1. 🛡️ Resilience Governance Engine Unleashed

LingFrame now features robust, unit-level micro-governance capabilities native to the JVM:

• Circuit Breaking: Employs a SlidingWindowCircuitBreaker to proactively trip the circuit when an individual unit exhibits a high failure rate, thwarting cascading system outages.
• Rate Limiting: Utilizes a TokenBucketRateLimiter to throttle massive traffic spikes aimed at specific hot-swappable units.
• Retry: Provides a zero-invasive, kernel-level retry mechanism for handling transient failures.
• Fallback: Works in tandem with the SmartServiceProxy to execute graceful degradation routines whenever a unit times out or gets short-circuited.
  All resilience parameters can be dynamically provisioned and updated via the GovernanceManager on the fly.

2. 🔄 Paradigm Shift in Terminology

To irrevocably resolve the conceptual ambiguities surrounding the historically overused term "Plugin", an exhaustive architectural refactoring was executed:

• The concept of Plugin has been officially codified as Ling (Unit).
• The concept of Host has been renamed to LingCore.
• The core descriptor specification mandates the use of ling.yml, discarding the legacy plugin.yml.
• Substantial monolithic renaming of core classes (e.g., PluginManager -> LingManager, PluginRuntime -> LingRuntime).

3. 🐛 Deep Mitigation of ClassLoader Memory Leaks

Hot-swapping logic inside the JVM inherently risks memory leaks arising from retained Classloaders. V0.2.0 addresses this extensively by:

• Aggressively evacuating dormant Singleton and Interceptor caches nested deeply within the Spring Sub-ApplicationContext upon unit teardown.
• Systematically severing static reference chains spanning ubiquitous libraries like Jakarta EL, Objenesis (used for CGLIB caching), and native logging frameworks.
• While JVM mechanics dictate cautious assertions, memory retention has been astronomically reduced across aggressive unit reload cycles—propelling LingFrame toward true industrial-grade stability.

4. 🔌 Expansive Ecosystem Backward Compatibility

Modern dynamic runtime manipulation is no longer restricted to the bleeding edge. LingFrame V0.2.0 extends robust support to legacy enterprise applications:

• Universally validated against JDK 8.
• Introduced the bespoke lingframe-spring-boot2-starter, assuring frictionless assimilation into legacy Spring Boot 2.7.x environments bridging javax.* boundaries.
• (Uncompromised support for Spring Boot 3.x is naturally preserved under lingframe-spring-boot3-starter).

5. 🛠 Developer Experience (DX) Enhancements

• DevMode: Instantiated the lingframe.dev-mode.enabled directive. In DevMode, units are auto-activated immediately post-installation, and extraneous authorization safeguards are relaxed—rendering local testing pipelines phenomenally smooth.
• SpringDoc API Clustering: The Swagger integration has been overhauled to intelligently cluster, segment, and label APIs unequivocally, distinguishing between underlying Host endpoints, Core APIs, and distinct dynamically inserted Ling endpoints.

---

This discussion was created from the release 灵珑·蜕变.