Wednesday, January 29, 2003
The project that Gelernter and several of his graduate students are working on is called Lifestreams, and it may completely change how we manage information. Today, our view of cyberspace is shaped by a 20-year-old metaphor in which files are documents, documents are organized into folders, and all are littered around the flatland known as the desktop. Lifestreams takes a completely different approach: instead of organizing by space, it organizes by time. It is a diary rather than a desktop.

Monday, January 27, 2003
Simple is a comprehensive Java framework for the development of HTTP services. The framework consists of an API for the development of Java HTTP services and a service engine to process services. The API provided enables HTTP service components similar to Java Servlets to be developed. Simple HTTP services provide functionality comparable to Servlets with much better support for concurrency and component chaining, and a much cleaner interface.

The goal of Simple is to provide an alternative to the Java Servlet API and address some of the shortcomings of the API, such as complexity and concurrency. Simple was originally developed as an interface layer between a Servlet engine and a Web server. As it turned out Servlet semantics did not suit high concurrency very well and did not allow individual objects to specify service semantics (other than single thread model). So the resulting project broke from the Servlet "standard" to provide an alternative, there are enough Servlet engines out there.

Very interesting. #

WSIF: Web Services Invocation Framework
The Web Services Invocation Framework (WSIF) is a simple Java API for invoking Web services, no matter how or where the services are provided. Please refer to the release notes before you proceed with using WSIF.

WSIF enables developers to interact with abstract representations of Web services through their WSDL descriptions instead of working directly with the Simple Object Access Protocol (SOAP) APIs, which is the usual programming model. With WSIF, developers can work with the same programming model regardless of how the Web service is implemented and accessed.

WSIF allows stubless or completely dynamic invocation of a Web service, based upon examination of the meta-data about the service at runtime. It also allows updated implementations of a binding to be plugged into WSIF at runtime, and it allows the calling service to defer choosing a binding until runtime.

Finally, WSIF is closely based upon WSDL, so it can invoke any service that can be described in WSDL.

So this is SOAP's answer to REST? Interesting, though it doesn't really solve the problem. "Protocol independence" might not be such a red-herring after all. Still... #

JavaLive Transcripts Index: High Performance GUIs with the JFC/Swing API
Welcome to JavaTM Live! Today's focus is on getting high performance with Swing-based GUIs. Our guests have a lot of performance-related and Swing-related experience. They're Java Performance Manager, Steve Wilson (co-author of the book Java Platform Performance), JFC/Swing technical lead, Scott Violet, and Java 2DTM API engineer, Chet Haase. They're ready to answer your questions about Swing-based GUI performance. So let's begin -- who has the first question?

Addressing Infosets with XPath
The XPath recommendation defines the official syntax for addressing Infoset subsets. The Infoset data model implies hierarchical relationships (child, parent, descendant, ancestor, and so on) between the information items that make up a document. XPath uses these implied relationships along with other filtering constructs to assist in identifying portions of the document (for example, find all child car elements whose make='BMW'). Before XPath, the only similar mechanisms available to developers were a few Document Object Model (DOM) APIs (getElementsByTagName, childNodes, and so on) and ID/IDREF relationships, which are of limited utility in terms of generic document addressing.

XML Namespaces and How They Affect XPath and XSLT
The first article in this series is about an often misunderstood facet of XML—namespaces. XML namespaces are an integral aspect of most of the W3C's XML recommendations and working drafts, including XPath, XML Schema, XSLT, XQuery, SOAP, RDF, DOM, and XHTML. Understanding how namespaces work and how they interact with a number of other W3C technologies that are dependent on them is important for anyone working with XML to any significant degree.

This article explores the ins and outs of XML namespaces and their ramifications on a number of XML technologies that support namespaces.

Sunday, January 26, 2003
Comparing SWT and Swing
SWT (standard widget toolkit) has been billed as the fresh new way to develop desktop applications in Java, and is claimed to offer performance on par with native applications and a look that exactly matches that of the native platform. Should developers stop writing their desktop applications in Swing and move to SWT? The answer is clearly NO! As this article will detail, Swing performance can, and often does, exceed that of the equivalent SWT app. Further, Swing can provide a look and feel that exactly matches that of the platform, provides a more consistent cross-platform story, and offers a level of flexibility far and beyond what is possible with SWT.


the server side
dotnet junkies
sam gentile
sam ruby
paul prescod
.net guy
jon udell
john robb
blogging roller
desktop fishbowl
cafe au lait
be blogging
kevin burton
james strachan
the truth is out there
brett morgan
blogging roller #2
joe's jelly
psquad's corner
rickard oberg
the saturn times
russel beattie
gerhard froelich
pete drayton
clemens vaster
ingo rammer
ken rawlings
simon fell
bit working
justin rudd
chris sells
john lam
jim murphy
brian jepson
john burkhardt
matt pope
better living through software
loosely coupled
understanding software engineering
rest lst,rdf-interest lst,tag lst ucapi lst

A man, his puppy, and a double barreled shotgun.

Powered by Blogger