The following is an extract from the above-mentioned
email newsletter,
dated April 24, 2001,reprinted courtesy of ITWorld.com:
The Java Message Services (JMS) API attempts
to provide an
infrastructure where an enterprise computing infrastructure's
elements
can exchange information with one another. That information may
include
requests for values or services, responses to requests, and event
notifications.
The JMS architecture is particularly adept at
exchanging messages
asynchronously; its facilities allow for slow, and perhaps
intermittent, connectivity between clients. For that reason, the
JMS
API particularly interests application developers for mobile devices
--
PDAs, mobile phones, etc?. Dr. Silvano Maffeis of Softwired, a
Swiss
provider of JMS solutions, has put together an excellent whitepaper
on
the subject of applying JMS to mobile devices. Entitled "Middleware
Support for Application-to-Application Wireless Messaging,"
the paper
(which requires you to cursorily register before downloading)
emphasis
Softwired's iBus product but still covers the general material,
and the
proprietary stuff is interesting anyway.
The best book I've yet seen on the subject of
JMS is "Professional JMS
Programming," by a team of Wrox Press programmers (including
Dr.
Maffeis, above). You can find that at
http://www.amazon.com/exec/obidos/ASIN/1861004931.
About the author(s)
-------------------
David Wall works as a freelance writer, programmer, lecturer,
and
consultant. Based near Washington, D.C., David has written and
co-
written several books, including Graphics Programming with JFC.
He
enjoys traveling, sailing, woodworking, and literary nonfiction.His
woodworking habit has come in handy for building those much-needed
bookshelves in the Dave Cave. He can be reached at
david.wall@javaworld.com.
