A wish list for browser evolution

Continuing on a long-running thread, two weeks ago, we talked about the browser stack versus RIA competition, and spent some time last week on the case against the browser stack.

Today, let's look at the other side. If an RIA has a scene graph or other visual object model, a scripting language, network conectivity, and some means of handling UI events and rendering content, well, doesn't that describe DOM + JavaScript + the browser, too? The browser stack continues to evolve, and maybe from the mile-high view, using ActionScript to manage a Flex video object isn't that different than using JavaScript to manage an HTML5 <video> tag.

But what does the browser stack need to do to keep the Ajax crowd happy? InfoQ points us to an interesting wiki-based poll on the topic, in What Do You Want On Future Browsers? Time to Vote! "An industry wishlist for future browsers has been collected and developed by OpenAjax Alliance. Using wiki as an open collaboration tool and with contributions from many people in the industry, the feature list now lists 37 separate feature requests, covering a wide range of technology areas, such as security, Comet, multimedia, CSS, interactivity, and performance. The goal is to inform the browser vendors about what the Ajax developer community feels are most important for the next round of browsers (i.e., FF4, IE9, Safari4, and Opera10) and to provide supplemental details relative to the feature requests"

Also in Java Today, the SDN has posted a Enterprise Tech Tipon Preventing Non-Repeatable Reads in JPA Using EclipseLink. "In this tip, you'll learn how to prevent non-repeatable reads through the Java Persistence API (JPA) and JPA extensions provided by EclipseLink. A non-repeatable read is a concept pertinent to database transactions. In a non-repeatable read, multiple reads of a data item from a datasource do not return the same value for the data item. In JPA terms, a non-repeatable read means that within a transaction, if an application reads the same entity multiple times from a datasource, the application will find that the entity state has changed between reads."

If an application is useful, then the network of users will grow crazily fast at some point. As more and more mission-critical applications are now running on Java EE, many Java developers are caring about scalability issues. However, most of popular Web 2.0 sites are built with script languages, and there are a lot of voices to doubt the scalability of Java Applications. In TheServerSide's article Scaling Your Java EE Applications, Wang Yu takes real world cases as examples to explain ways on how to scale Java applications based on his experiences on the laboratory projects, and at the same time, bring together practice, science, algorithms, frameworks, and experience on failed projects, to help readers on building high scalable Java applications.

The latest Java Mobility Podcast is Java Mobility Podcast 52: Wireless Industry Partnership and Top Ten Dating Tips For Developers. Caroline Lewko from WIP shares how WIP helps developers negotiate the mobile ecosystem and talks about the new Mobile Developer Wiki that's currently in Beta. We finish up with two selections from her popular talk Top Ten Dating Tips for Developers.

Today's Weblogsstart with a guide from Inderjeet