The current status of the RTSJ and JSR 282

摘要

to support better feasibility analysis.11. Review the current support for real-time garbage collectors, and expand it if necessary.12. Associate a scheduling eligibility value with asynchronous events.13. Permit all errors associated with exceeding RTSJ resource limits to fire asynchronous events (or alternatively, release asynchronous events event handlers). Currently some of them can only throw exceptions.14. Add new methods as necessary to consistently provide both a method that creates a returned object and one that takes a destination wherever those forms are appropriate.15. Update the documentation for the physical memory classes to improve their clarity. Make the minimum modifications to the semantics and APIs required to fix any problems that justify such changes.16. Update the semantics for cost enforcement to permit support of the invariant that a schedulable's CPU use in each period is bounded bythe cost.17. Consider compatible modifications to the RTSJ that would make it easier to limit the use of immortal memory.18. Modify the specification as required to clarify any interaction with Java#8482; 5.19. Consider hierarchical processing group parameters.20. Consider improvements to the wait-free queue classes, or possibly new classes with similar services.21. Consider enhancements to the async event system to let events carry data.The talk will present the current status of these and other developments.