By DJ Adams
January 2002
Pages: 480
ISBN 10: 0-596-00202-5 |
ISBN 13: 9780596002022
![]()
![]()
![]()
![]()
(Average of 2 Customer Reviews)
Programming Jabber offers developers a chance to learn and understand the Jabber technology and protocol from an implementer's point of view. Detailed information of each part of the Jabber protocol is introduced, explained, and discussed in the form of mini-projects, or simple and extended examples in Perl, Python, and Java. This book provides the foundation and framework for developers to hit the ground running, and is the essential book on Jabber.
Full Description
- Showing you how to install and configure the Jabber server
- Providing a detailed overview of the server architecture and configuration options
- Covering the core Jabber technologies such as XML streams and Jabber identifiers
- Referencing all of Jabber's XML namespaces
- Examining the client registration and authentication phases
- Showing how to deploy your own Jabber-based messaging solutions
- Demonstrating how to embed XML-RPC-style call mechanisms into Jabber
Register your book | Submit Errata | Examples | Author's Article | DJ's Weblog | OSCON 2002 Session
Browse within this book
Cover | Table of Contents | Index | Sample Chapter | Colophon
Book details
First Edition: January 2002
ISBN: 0-596-00202-5
Pages: 480
Average Customer Reviews: ![]()
![]()
![]()
![]()
(Based on 2 Reviews)
Featured customer reviews
Programming Jabber Review, March 26 2002
The Scenario
Jabber was first conceived by Jeremie Miller (pic) in early 1998 in an effort to unify the disparate instant messaging networks. Instant Messaging networks rely on the network effect to gain and retain marketshare. The concept is the same when applied to any sort of participatory network whether it's a junk exchange, or content exchange, the value of the network increases with the square of the number of participants.
If this is true, then doesn't it follow that it is in the best interests of the IM networks to establish peering agreements with each other so that their users can directly contact users on other networks without having to install each client?
Hello Jabber.
When I first picked up this book, I expeted to understand the Jabber protocol in sufficient depth to implement my own IM client. Instead, the approach this book takes is that Jabber isn't just an XML-based protocol strictly for IM, rather it is a general purpose event notification protocol that has some very nice message routing and user management features built into it. While i was reading about the messages that Jabber has defined as part of the protocol, I could easily see other applications/devices generating Jabber messages to notify subscribers (either other systems, or people) of events.
Part 1 of the book focuses on getting you up to speed on the basics of Jabber technology: motivation, major features, XML protocol sample and compiling/configuring your own Jabber server. Chapter 2 presents the "10,000 foot view" of Jabber technology. In here you will find a sample client-query request/response flow with full HTTP headers, discussed step by step. The next two chapters are a very in-depth discussion of installing and configuring your own Jabber server. When you dive into a custom configuration of a fleet of Jabber servers (a "constellation" in Jabber terminology), it really starts to hit home that the real problem that Jabber solves is far deeper than just IM.
From there, part 2 kicks off with a detailed discussion of the most basic building blocks of Jabber technology: resource identifiers, XML handling mechanism and the set of XML elements/attributes that make up the vocabulary of the Jabber protocol. Each element/attribute is presented with an annotated example and sample client/server interactions where appropriate. Examples can make or break a technical book, and these examples do a good job of illustrating how the element/attribute is used.
The following chapters take you through using standard Jabber features, user registration/authorization, messages, presence, groupchat, components and the event model to enable new applications. One very interesting application that presented is enabling developers to receive CVS commit notifications via Jabber.
<h3>What's Bad?</h3>
I know the development community is suspicious of glowing book reviews where everthing is wonderful and nothing could be done to improve the book, so I'll nitpick. My major problem with this book is that the overwhelming majority of the sample applications are written in PERL/TK. This isn't a problem in and of itself, but I'm not a PERL/TK developer. If I build a Jabber solution, it will be in java, so PERL/TK samples don't do me a lot of good. I think equal time should be given to implementing Jabber using the 2 most used languages, as defined by the number and activity of open source projects using Jabber technology.
What's Good?
This book covers everything relevant to Jabber technology, from lowest level innerworkings and extensibility examples for developers to configuration and deployment for admins. Most of the book is spent looking directly at the Jabber XML protocol, instead of a specific API implementation. This way, the book covers the technology and doesn't get lost in how one particular API models the protocol.
So What's In It For Me?
If you want to implement an inside-the-firewall IM solution for your company/group/tribe or investigate integrating event notification into an application, this is a great starting point. If you're just curious about Jabber and want to know how it works, then this will give you enough information to get you hooked.
Programming Jabber Review, February 18 2002
As a disclaimer, I have been involved with Jabber for 3 years, am the author of one of the more popular Jabber clients for linux, and am a friend of DJ's.
Jabber finally has its Bible. DJ has written an excellent introduction into the world of Jabber, covering everything a programmer would need to become familiar with the protocol for this Open instant messaging system. He covers everything from the basics of what exactly Jabber is, how to deal with presence, messages, and basic extensions, all the way up to complicated and unfinished extensions such as XML-RPC. Anyone programming Jabber needs this as a reference, and anyone looking to get started in the Jabber world need not look further than this book.
Media reviews
"'Programming Jabber' is a resource that Jabber programmers won't want to be without."
--Paul Barry, "Linux Journal," May 2003
"'Programming Jabber' is written for the programmers who will develop novel functionality based on Jabber. The book's clear explanations of underlying principles fit it well for that role. The examples are a particular strength in illustrating that Jabber can and should transport messages between computer processes as well as between humans...Working developers who use a variety of languages and who have a broader interest than just IM should start their projects with careful study of 'Programming Jabber.'"
--Cameron Laird, UnixReview.com, June 3, 2003
http://www.unixreview.com/documents/s=8274/ur0306c/
"There is some good documentation on the www.jabber.org web site, but you'll find O'Reilly's 'Programming Jabber' even more useful."
--Simon Bisson, Application Development Advisor, December 2002
"This book covers everything relevant to Jabber technology, from lowest level inner workings and extensibility examples for developers to configuration and deployment for admins. Most of the book is spent looking directly at the Jabber XML protocol, instead of a specific API implementation. This way, the book covers the technology and doesn't get lost in how one particular API models the protocol. If you want to implement an inside-the-firewall IM solution for your company/ group/tribe or investigate integrating event notification into an application, this is a great starting point. If you're just curious about Jabber and want to know how it works, then this will give you enough information to get you hooked."--Craig Pfeifer, slashdot.org
"Quite simply, Programming Jabber rocks! When reviewing the book, I often found myself reading along, having a good time and getting excited about Jabber instead of looking to see if something was wrong or missing." --Jeremie Miller, Founder and Lead Developer of Jabber






