Revision as of 21:42, 19 June 2017 edit Widefox (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, IP block exemptions, New page reviewers, Pending changes reviewers, Rollbackers 110,632 edits m →top: sp, rm selflink ← Previous edit		Revision as of 22:02, 19 June 2017 edit undo Widefox (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, IP block exemptions, New page reviewers, Pending changes reviewers, Rollbackers 110,632 edits m →top: inline EXT -> ref Next edit →
Line 9: * event handling. 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] ~~from [[PTC, Inc.]],~~</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.

Real-time Java: Difference between revisions