Java's Creator James Gosling talks with Bill Venners about the current state of the Java language.
Bill Venners recently spoke with Sun Microsystems Vice President and Fellow James Gosling at his Sun Labs office in Mountain View, Calif. In this interview, Java's creator imparts his thoughts on enterprise software, algorithms, the trend towards user-oriented software, flexibility, complexity, and other aspects of the art of computer programming.
Artima.com columnist Frank Sommers interviews Rob Gingell, Sun Microsystems' fellow and chief engineer and chair of the Java Community Process, about the pressures on vendors to both create froth—to add value on top of standards—and maintain compatibility in a multi-vendor industry.
by Frank Sommers, January 13, 2002, 1 comment
Inaugurating the JCP Watch Series, Artima.com columnist Frank Sommers interviews Sun Microsystems' fellow and chief engineer Rob Gingell, chair of the Java Community Process (JCP), about open source licensing, source and binary compatibility, binary standards, and the JCP.
On Monday, December 10, 2001 Bill Venners visited the Sun Microsystems campus in Santa Clara, California to interview Josh Bloch, an architect in the Core Java Platform Group. In this interview, Josh discusses many aspects of design.
Frank Sommers and Bill Venners recently caught up with Jini architect Jim Waldo at JavaWorld's San Francisco office. In this interview, Waldo talks about the impact of mobility on distributed systems, Jini as a tool to reengineer the corporate MIS infrastructure, the importance of type systems, and the semantic web. (November, 2001)
The Jini Transaction Specification defines a transaction coordinator for the two-phase commit protocol, as well as a default transaction semantics guaranteeing ACID properties. This article explains the default transaction semantics, and offers guidelines for its implementation in services based on activatable RMI objects.
Developers should distinguish between the systems themselves and the computations they wish to perform on them. While a distributed system, or parts of it, might fail occasionally, computations performed on those systems can still be highly dependable. This shows how multiple Jini services can dependably cooperate via transactions.
Java's Creator James Gosling talks with Bill Venners about many topics, including complexity, simplicity inheritance, composition, JSPs, servlets, and more.
In the future, the industry will be motivated to develop dependable methods of software-to-software interaction on the network, where unreliable components will be eliminated automatically, resulting in the survival of the fittest services. This article is the first in a four-part series on designing and deploying highly dependable Jini services.
The ServiceUI specification developed by the Jini.org community defines a suggested procedure for attaching user interfaces to Jini services. In this article, Jeffrey Peden introduces you to a simple ServiceUI-based example service. Then he shows you how to build an application for browsing and launching user interfaces for Jini services.
In this article, Frank Sommers provides background to the use of mobile objects in Jini, and describes the Java class loading and object serialization architectures that make mobile code possible. He then offers a tutorial on setting up Jini services so that you can make your code available for download by clients.
In this article, Bill Venners compares objects and documents from a user's perspective. Whereas the previous articles in the series focused on clients that operate autonomously, this article focuses on clients that connect network-delivered services to human users.
In this article, Susanne Hupfer introduces you to distributed data structures -- the common set of building blocks that are used in practically every space-based program. She shows you how to build and use a versatile channel distributed data structure, and illustrates its use in a distributed MP3-encoding application.
This article fleshes out the advantages and disadvantages of objects compared to documents when sending a service across the network to software, in the absence of a client-side user.