Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

JCP Votes Down JSR 323

DZone's Guide to

JCP Votes Down JSR 323

· Java Zone ·
Free Resource

Atomist automates your software deliver experience. It's how modern teams deliver modern software.

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.

Get the open source Atomist Software Delivery Machine and start automating your delivery right there on your own laptop, today!

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}