JTRES 07
Last week we held the 5th annual Java Technologies for Real-Time and Embedded Systems Workshop in Vienna, Austria at the Technical University of Vienna. This is the place to be if your working on or with the RTSJ and other ideas and designs around using the Java Platform or Language for applications needing temporally predictable execution behavior.
I served as program committee chair this year. The proceedings are published in the ACM Digital Library as they were last year.
We had 34 papers submitted and accepted 25 for presentation and publication. In the program were also, one keynote by Laurie Tolson and John Pampuch (executives at Sun Microsystems), 4 invited talks, two panels, and one BoF. Needless to say the attendees were busy for two and a half very full days.
Martin Schoeberl did an outstanding job as General/Local chair. All the necessary things happened as they should and the social events were memorable. Thursday night every one went for a ride on a really big Ferris Wheel (like the London Eye but older and a bit smaller) the dinner at a great, truly Austrian restaurant. The menu included a whole, barbecued pig....
During the BoF I proposed two initiatives which were enthusiastically accepted by the community.
First, starting with the great work and presentation of Brian Doherty in which he told us about how he modified the SPEC jbb benchmark to more accurately show true response times of the transactions. Sun will be proposing to SPEC that this work form the basis of a new SPEC benchmark specifically designed to measure the predictability of RTSJ implementations. I feel our community is in dire need of such a formal, accepted, accurate benchmark if we are to serve our customers well. I, Sun, invited everyone to participate with us at SPEC in the creation of the benchmark.
Second, It's been clear to me for a while that the RTSJ might be more aggressively implemented and marketed if there were a way to leave out some of the more exacting features, specifically the no-heap execution mode (NHRT's, ImmortalMemory, ScopedMemory, etc.). This mode allows temporal precision (in the tens of microseconds in typical implementations) which is really overkill for many, many real-time applications. So, the proposal was to initiate a new JSR, co-led by Sun and IBM to define the partition. The Original RTSJ (as defined in JSRs-1/282) will be called, Tor and the new piece, which will be a strict subset of Tor, we called, Sue, (for, a Subset that Useful but Easy to implement). We expect this to be a rather quick effort. Once done, we'll have Peter Dibble and TimeSys create the necessary partitioning in the RI and TCK. I expect that more and new implementations of real-time Java will embrace Sue and move forward quickly on compliance with Peter's new TCK. Of course, at Sun, we'll continue with our Tor implementation.
Posted at 12:24PM Oct 05, 2007 by gregbollella in Sun | Comments[0]