| Similar Articles |
|---|
 |
JavaWorld
March 2003
Amit Goel & David Marshall |
Manage users with JMS This article describes a simple solution to the common problem of maintaining consistent user information across various business applications.   |
JavaWorld
November 2001
Kurt Jacobs |
Subscribe now for rapid prototyping Developers often find themselves reengineering an API to meet the demand of evolving requirements. By providing a framework for a more flexible system, the Publisher-Subscriber pattern can help you overcome some problems associated with object dependencies... |
JavaWorld
February 2001
Tarak Modi |
Add the power of asynchronous processing to your JSPs The author shows how to bring the power of Java Messaging Service to JavaServer Pages developers who are excellent at content development but not interested in the intricacies of asynchronous programming... |
JavaWorld
March 2002 |
Letters to the Editor JavaWorld readers warn about synchronization; present a Servlet 2.2-compliant solution for mixing protocols in Web apps; suggest using the Data Object Access design pattern with the Value Object design pattern... etc. |
JavaWorld
October 2002
Thomas Laramee |
Should you go with JMS? Java developers must often determine whether JMS meets their requirements as a message-processing layer for their distributed systems. Issues such as application server performance, data distribution, security, and error handling must be considered. |
PC World
December 2005
Andrew Brandt |
Privacy Watch: Who's Your Software Talking To? Delving into the sources of a PC's heartbeats. |
