Content deleted Content added
Tags: Mobile edit Mobile web edit |
Added pre-history (i.e. before Java Community Process) description of real-time Java. |
||
Line 9:
* event handling.
The initial [http://www.cs.cornell.edu/courses/cs614/1999sp/papers/rtji.pdf proposal] for an open standard for real-time Java was put forth by Kelvin Nilsen, then serving as a research faculty member at Iowa State University. A follow-on overview paper was published in the [https://dl.acm.org/doi/abs/10.1145/276609.276619 CACM]. The overwhelmingly positive response to these early proposals resulted in a series of meetings hosted by the National Institute of Standards and Technology in an effort to establish an open standard for real-time Java. NIST was ultimately told that they were not the appropriate body to establish standards related to the Java language, as Java was trademarked, and the technologies were owned by Sun Microsystems. Therefore, NIST ended their efforts with publication of consensus [https://www.itl.nist.gov/div897/ctg/real-time/rtj-final-draft.pdf requirements] that could be considered by future standardization efforts to be hosted by Sun Microsystems..
To overcome typical real time difficulties, the [[Java Community Process|Java Community]] introduced a specification for real-time Java, JSR001. A number of implementations of the resulting ''Real-time specification for Java'' (''RTSJ'') have emerged, including a [[reference implementation (computing)|reference implementation]] from [[TimeSys|Timesys]], [[IBM]]'s WebSphere Real Time, [[Sun Microsystems]]'s Java SE Real-Time Systems,<ref>[http://java.sun.com/javase/technologies/realtime/index.jsp Java SE Real-Time Systems]</ref> PTC Perc from [[PTC, Inc.]],<ref>[http://www.ptc.com/developer-tools/perc PTC Perc]</ref> or [[JamaicaVM]] from [[aicas]].▼
▲
The RTSJ addressed the critical issues by mandating a minimum specification for the threading model (and allowing other models to be plugged into the VM) and by providing for areas of [[memory]] that are not subject to garbage collection, along with threads that are not preemptable by the garbage collector. These areas are instead managed using [[region-based memory management]]. The latest specification, 2.0, supports direct device access and deterministic garbage collection as well.
Line 24 ⟶ 26:
==External links==
* [http://www.cs.cornell.edu/courses/cs614/1999sp/papers/rtji.pdf Issues in the Design and Implementation of Real-Time Java]
* [http://aicas.com/cms/en/rtsj Real-Time Specification for Java 2.0 (RTSJ 2.0)]▼
*[https://dl.acm.org/doi/abs/10.1145/276609.276619 Adding Real-Time Capabilities to Java]
*[https://www.itl.nist.gov/div897/ctg/real-time/rtj-final-draft.pdf Requirements for Real-Time Extensions for the Java Platform]
* [http://jcp.org/en/jsr/detail?id=282 JSR-282]
* [http://www.rtsj.org/ Real-Time Specification for Java (RTSJ)]
| |||