Lesson plan

Real time Java

Real-time Java is a catch-all term for a combination of technologies that enables programmers to write programs that meet the demands of real-time systems in the Java programming language. Java's sophisticated memory management, native support for threading and concurrency, type safety, and relative simplicity have created a demand for its use in many domains. Its capabilities have been enhanced to support real-time computational needs: * Real-time Java supports a strict priority-based threading model, * because Java threads support priorities, Java locking mechanisms support priority inversion avoidance techniques, such as priority inheritance or the priority ceiling protocol, and * event handling. The initial 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 Communications of the ACM. 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.…

Back to article

Article summary

Real-time Java is a catch-all term for a combination of technologies that enables programmers to write programs that meet the demands of real-time systems in the Java programming language. Java's sophisticated memory management, native support for threading and concurrency, type safety, and relative simplicity have created a demand for its use in many domains. Its capabilities have been enhanced to support real-time computational needs: * Real-time Java supports a strict priority-based threading model, * because Java threads support priorities, Java locking mechanisms support priority inversion avoidance techniques, such as priority inheritance or the priority ceiling protocol, and * event handling. The initial 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 Communications of the ACM. 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.…

Key claims

  1. P10283: C132106392 — source: Wikidata · confidence 0.95
  2. P31: Q7397 — source: Wikidata · confidence 0.95
  3. P6366: 132106392 — source: Wikidata · confidence 0.95
  4. P646: /m/08x8dn — source: Wikidata · confidence 0.95

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. The record states that the P10283 is "C132106392". What evidence would count against this claim?
  3. The record states that the P31 is "Q7397". What evidence would count against this claim?
  4. The record states that the P6366 is "132106392". What evidence would count against this claim?
  5. The record states that the P646 is "/m/08x8dn". What evidence would count against this claim?
  6. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  7. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.