Taking This Further
The journey through the recipes in the last three chapters of the book has taken us from the simplest CVS notification mechanism with the cvsmsg script (Section 8.1) through a fairly involved RSS component (Section 9.3) to the transporting of XML-RPC-encoded requests and responses with our JabberRPCRequester and JabberRPCResponder scripts (Section 10.3).
This chapter, and indeed the book, ends on a simple note, in the form of the approv script. Not without reason, we’ve completed the circle of script and application complexity. While we can build very useful and successful applications that are naturally complex, a Jabber-powered solution doesn’t necessarily have to be. To employ the Jabber philosophy, the technology, and the protocol elements to build bridges between previously separate systems, and to span different areas of technology, open and proprietary alike, using Jabber’s open, extensible, and flexible protocol, is what it’s all about.
Finally, it’s hopefully clear from the diversity of recipes shown in this part of the book that deploying solutions with Jabber, as noted in the preface, really is fun!
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access