Alex Miller lives in St. Louis. He writes code for a living and currently work for Terracotta Tech on the Terracotta open-source Java clustering product. Prior to Terracotta he worked at BEA Systems and was Chief Architect at MetaMatrix. His main language for the last decade has been Java, although Alex have been paid to program in several languages over the years (C++, Python, Pascal, etc). Alex has posted 43 posts at DZone. You can read more from them at their website. View Full User Profile

JCP Votes Down JSR 323

01.24.2008
| 3517 views |
  • submit to reddit

I wrote recently about an interesting JSR proposal JSR 323 - Strong Mobility for Java. This proposal concerned allowing the full running state of a Java program to be serialized and deserialized to continue running elsewhere.

In interesting news, the JCP just voted down JSR 323 with 8 no votes and 3 abstentions. It seems like the consensus was that both the technology is premature and that no such standard is needed. Some of the more interesting comments below.

Sun:

Sun believes this could be an interesting area of research, but does not yet see the kind of community or vendor support that would motivate standardizing on a mechanism in the JCP. Currently we think that os virtualization techniques are providing more complete solutions for the kind of problems outlined in this proposal.

Intel:

Generally, for standardization in JCP, the request should represent the interests of varied approaches to a problem or various alternative implementations where there is a community that needs standardization in order to progress. We don't see evidence for that in this JSR. We also aren't convinced that, if this were to be done in JCP, it isn't better to do it in the VM rather than as in this proposal. Research in this area seemed to have tailed off a few years ago without any consensus, with interest shifting to hypervisor based virtualization. We aren't convinced there is a need for the standardization suggested in this JSR.

Doug Lea:

This work is not ready for a JSR. I encourage the proposers to work on and gain experience with implementations before re-proposing as a JSR.

Published at DZone with permission of its author, Alex Miller.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Tags: